Release #: 2026.11.1
Release Date: November 18th, 2026
What's New
This release adds received AI Cards, Bills of Materials and shared vulnerabilities in the Public API, and API clients can now set a vulnerability's status. It also adds AWS connections for CloudSensor, a Search widget on the Dashboard, and update statuses and refresh schedule history on recurring AI Card requests. Improvements include a Connection column in Cloud Assets, the package ecosystem on technology vulnerabilities and tables that keep their state. Bug fixes include clearer permission errors in the Public API and in the application. Two changes need action from you and are listed first.
Action Needed
- Public API permission errors. For tenants licensed for the Public API, a request the API client is not permitted to make now returns a 403 error that names the missing permission. It previously returned a 401. If an integration treats every 401 as a signal to refresh the token and retry, update it to handle a 403 as a permission problem.
- API role for setting a vulnerability's status. Setting a vulnerability's status through the API needs the new Vulnerabilities Update API permission, which is not on the Default API Role. Create an API role that includes it and assign that role to the API client.
Feature Additions
Received AI Cards, BOMs and Vulnerabilities in the Public API
If you receive AI Cards from vendors, you can now read those cards, the vendors' Bills of Materials and the shared vulnerability data through the Public API. Before this release this data was only available in the application. You can list received cards and filter them by vendor, status and update time, read each card's artifacts, read its BOM items, and read a vulnerability summary and vulnerability feeds for one card or across all received cards. No role change is needed, since the AI Cards, Bill of Materials and Vulnerabilities read permissions are already on the Default API Role. Keep these points in mind:
- A card's
vendorIdis filled in only after the vendor has been opened in My Vendors. Until then, filtering byvendorIdreturns no results. publishedAtis when the card was delivered to your tenant, not when the vendor published it.- A model vulnerability's
findingIdchanges when the model is retested. A technology vulnerability'sfindingIddoes not change. - If the vendor has not shared vulnerability data for a card, the card's vulnerability feeds return a 409 error with the code
VULNERABILITIES_NOT_SHARED.
See Pagination & Incremental Sync for details.
Set a Vulnerability's Status Through the Public API
API clients can now mark a vulnerability as Resolved, Ignored or Unresolved, the same as on the Vulnerabilities page, with PUT /api/public/vulnerabilities/{uniqueId}/status. A reason of up to 2,048 characters is required for Ignored. The status applies to the package within the Bill of Materials, so every component in that BOM that uses the same package changes with it. This route needs the new Vulnerabilities Update API permission, which is not on the Default API Role. To use it, an administrator creates an API role that includes the permission and assigns that role to the API client. See Technology Vulnerabilities for details.
AWS Connections for CloudSensor
Tenants licensed for CloudSensor can now connect AWS accounts in Integrations > CloudSensor Integrations, alongside Azure. The connection form has a new Cloud Provider field, and the account field becomes Azure Tenant ID or AWS Account ID. The provider and account cannot be changed after the connection is created. Creating a connection for either provider now opens a guided setup with Details, Consent (Azure only), Grant access and Verify access steps. For AWS, the set up AWS access link on the connection's row shows the External ID, the IAM permissions needed, a one-click CloudFormation deployment and the CloudFormation and Terraform templates. Finish stays disabled until access is verified, and the role must exist before access can be verified. So for AWS, choose Skip for now, deploy the role with set up AWS access, and then use verify access. The access check reports what Cranium can read and lists any missing AWS actions. The connections table has new Provider and Account ID columns. Verify Access and the verify access link now need the CloudSensor Integrations Update permission, which only the Admin role has by default. On an existing Azure connection, running verify access now updates its status, and a connection that fails the check moves out of ACTIVATED. See CloudSensor Overview for details.
Search Widget on the Dashboard
The Dashboard has a new Search widget that finds technologies, models and agents by name across Bills of Materials and cloud environments. It shows the top five results with their Asset Type and Source. Each result opens the asset where it was found, and a link opens the full Search page with your term filled in. The widget appears first on the Dashboard by default, including for users with a saved layout, and you can move or hide it with Customize Dashboard. Anyone who can open the Dashboard can use it, and cloud results also need Cloud Assets read permission. The widget is not on the limited-access Dashboard. The Quick Links widget is removed. See My AI Dashboard Overview and Asset Search Overview for details.
Update Status and Refresh Schedule History on AI Card Requests
A completed AI Card request on a refresh schedule now shows Completed · Update Pending or Completed · Update Overdue while its next cycle is open, and Completed otherwise. This applies in Outgoing Requests and Incoming Requests, and the status filter offers all three separately. As a result, filtering on Completed now returns fewer requests. Due-date tags now appear on these completed requests, and the overdue tile on My Vendors also counts completed requests whose next update is overdue. In Outgoing Requests, the history icon in the Refresh Schedule column opens Refresh Schedule History, which lists each change with When, Changed by and What changed. The history is visible to the requester only, not to the vendor, and it starts from this release. See Managing Outgoing AI Card Requests and Responding to an AI Card Request for details.
Improvements
Connection Column and Decommissioned Status in Cloud Assets
The Cloud Assets page has a new Connection column and filter that show which connection each asset came from, or Unavailable if the connection was deleted. Decommissioned datasets, endpoints, notebook runtimes and Workbench instances now show Decommissioned. Long lists now scroll to the last rows and the pager. No action is required. See CloudSensor Overview for details.
Package Ecosystem for Vulnerabilities
Technology vulnerabilities now record the package's ecosystem, such as PyPI or npm, so a package name that exists in two ecosystems no longer mixes their advisories. The Language column now shows Language (Ecosystem). The vulnerability CSV export adds Language, Ecosystem and EcosystemInferred columns, and the Public API vulnerabilities feed adds matching language, ecosystem and ecosystemInferred fields. Advisories that were mixed before are separated when the project is next scanned. AI Cards published before this release show the ecosystem only after the vendor republishes them. See Vulnerabilities Overview and Technology Vulnerabilities for details.
Tables Keep Page, Sort and Search in the Page Address
Most tables now keep their page, page size, sort and search in the page address. Back returns you to the previous table state, and reloading the page or sharing its link restores it. Tables inside dialogs and drawers are not kept, and vulnerability filters stay out of the address. No action is required.
Dashboard Widgets Follow Your Permissions
A user whose role lacked the permission for any one Dashboard widget was sent to an error page. The Dashboard now opens and hides only the widgets the user is not permitted to see, both on the Dashboard and in Customize Dashboard. The saved layout is kept, so a widget returns to its place if the permission is granted later. The Discovery and Inventory widget now needs read permission for RapidScan settings, in place of create permission. No action is required. See My AI Dashboard Overview for details.
Export Vulnerabilities on AI Systems
The Models and Technologies tabs on an AI System's Vulnerabilities tab have a new Export Vulnerabilities action for that AI System. Export all data includes all of the AI System's vulnerabilities, and Export filtered data applies the tab's filters and search. The tabs now also say when an AI System has no vulnerabilities to show or could not be loaded. No action is required. See AI System Details Overview for details.
Partially Failed Discovery Status
A VCS discovery scan now reports Completed when all projects succeed, Failed when all fail and Partially Failed when some fail. Partially Failed is a new Discovery Status filter option, and its row action is Detect AI. Projects that never ran are now marked as failed. Earlier scans keep their recorded status until you run discovery again. See Integrations Overview and Detect AI Overview for details.
Bug Fixes
- Fixed an issue where the Public API returned an empty 401 when the API client was not permitted to make a request, which looked the same as an expired token. For tenants licensed for the Public API, the request now returns 403 Forbidden with an explanation, and a
requiredPermissionfield names the permission to grant to the API client's role. A request that matches no permitted route, such as a wrong path, a wrong HTTP method or a malformed ID, also returns 403 with norequiredPermission. If Cranium cannot check permissions for a moment, the API returns 503, so retry after a short wait. An invalid or expired token still returns 401. In the application, a page your role does not grant now shows a 403 page that names the required permission, in place of a 401 page. See Authentication & Generating Credentials and Users, Roles & Access Management for details. - Fixed an issue where a push to a repository's default branch on GitHub or GitLab rescanned every BOM on the repository and overwrote BOMs that track other branches. BOMs that were already overwritten are not repaired, so rescan BOMs that track a non-default branch.
- Fixed an issue where Azure DevOps discovery saved no projects when a project in the integration's filter was deleted or inaccessible. That project is now skipped, so run discovery again to pick up the missing projects.
- Fixed an issue where turning SCIM welcome emails off did not save. If you turned them off before this release, turn them off again.
- Fixed an issue where a filtered Models vulnerability export was often empty or incomplete. Run again any filtered Models export taken before this release.
- Fixed an issue where Date Sent on received AI Card tiles showed when the card was accepted. It now shows when the vendor sent it, or N/A if unknown.
- Fixed an issue where a vendor could answer a declined AI Card request through the API. Requests already reopened this way are not changed back.





