Release notes
The collector is released by version, and you choose when a unit gets a new one. The hosted service (the web app, the API and the MCP server) always runs the current version, so its changes are listed by date. How long each part gets security updates is on Support periods.
Collector
Section titled “Collector”Released 16 November 2026. Security updates until 16 November 2031.
- Runs as its own user. The service now runs as the user
affectra-collector, not as root, with no capabilities, network access only, and the file system read-only apart from the outbox. The package creates the user. See Files the package installs. --pushneedshttps://. The collector refuses to push to anhttp://URL, because the API key would travel unencrypted. For a test against a local API, add--insecure. See Flags.- Long release files no longer stop reports. A
PRODUCTorVARIANTline that is too long is shortened, so the API accepts the report instead of refusing every one. - Bundle file names stay in the outbox. A unit ID can no longer make the collector write a bundle outside its output directory.
Settings are unchanged. An upgrade keeps your collector.env and keeps a running timer running.
Released 10 November 2026. Security updates until 10 November 2031.
- Reports name the collector’s version. Each report carries the version that
affectra-collector --versionprints. Under Units, the Collector field of a unit shows it, so you can see which units still run an old collector.
Settings and installation are unchanged. An upgrade keeps your collector.env and keeps a running timer running.
Released 10 November 2026. Security updates until 10 November 2031. The first release.
- Installed packages with package URLs. The collector reads the packages installed by dpkg (Debian, Ubuntu) or apk (Alpine) and reports each one with a package URL, so Affectra can match the unit against vulnerabilities. See What the collector reports.
- Online or air-gapped. A unit pushes its report to the API, or writes it as a bundle file to carry out. See Air-gapped units and bundles.
- The release a unit runs.
/etc/affectra-releaseholds the version, orPRODUCT,VARIANTandVERSIONlines, so Affectra can link the unit to a release. See Find affected units. - Packages for Linux
amd64,arm64andarm7:.deb,.rpmand tarballs, withSHA256SUMSto verify them. See Install the collector.
Hosted service
Section titled “Hosted service”16 November 2026
Section titled “16 November 2026”Web app 0.1.7, API 0.1.8.
- Check your GitHub organization link. Affectra now checks that the person who links a GitHub organization is an admin of it. A link saved before this check adds and removes nobody until an admin of the GitHub organization saves it again; its card says so. See Let a GitHub organization join.
- SBOMs up to 16 MiB. An upload may now be at most 16 MiB, with at most 30,000 components and 150,000 dependencies. A larger file is refused with
413. Upload one SBOM per product or image if yours is bigger. See Size. - Units to upgrade. The overview counts the units that still run a release with a finding that is affected or known exploited, and splits them into those that can upgrade to a newer release now and those waiting for a fix. The Upgrade filter under Units lists them. See See which units to upgrade.
- To assess and affected. The overview’s Open findings is now To assess: the findings that still need your assessment. Findings assessed as Affected are counted apart, and release lists show both, for example 8 to assess · 1 affected. Most exposed releases lists releases past their support end last. See What the numbers count.
- Choose your vulnerability feeds. An admin or owner can turn off NVD or a CSAF provider for your organization under Settings, through the API, and an assistant sees which feeds are on. See Choose vulnerability feeds.
- Fewer NVD findings that don’t apply. For an NVD entry that is affected only on certain platforms, Affectra now checks the operating system and device your SBOM names. If it names a different one, there is no finding. See Why a finding is or isn’t shown.
- Releases newest first. Releases are listed newest version first, so
1.10.0comes before1.9.2. Releases shows each product with its newest releases per variant, and Show all opens the product with a table of all of them. See Find a release. - Webhook endpoints in a side panel. Select an endpoint to open its panel: Send test event, New secret and Delete, its delivery log under Deliveries, and under Settings its events, language and URL, or turn it off. See Webhooks.
- More findings for Python, Java, Ruby, .NET and PHP packages. Affectra now compares PyPI, Maven, RubyGems, NuGet and Packagist versions with each ecosystem’s own rules, as OSV does, and checks the version ranges of their advisories. Before, it only used the advisories’ lists of versions, so advisories that give only a range were missed. Releases with such packages can show new findings after the next matching run. An advisory that only lists versions no longer makes the sources disagree. See Why a finding is or isn’t shown.
- Daily digest of agent proposals. Members, admins and owners can get one email a day that lists the agent proposals waiting for their decision, only on days when a new one was filed. An admin sets the time and time zone under Settings. See Daily digest of agent proposals.
- Finding lists come in pages.
GET /v1/orgs/{org}/releases/{release}/vulnerabilitiesandGET /v1/orgs/{org}/releases/{release}/finding-groupsnow answer{ "items": [...], "next": "...", "more": true }instead of a bare array: 50 items by default, up to 200 withlimit, and the next page withafterset tonext. Scripts that read these lists must followmore; see Check the result. The release page loads its findings a page at a time and has a Load more button. Finding groups now carry theirvendor_advisories. Lists of pending proposals that the web app reads in full (carry-overs, link proposals) say when there are more than it could load. - The unit list comes in pages.
GET /v1/unitsandGET /v1/orgs/{org}/unitsnow answer{ "items": [...], "next": "...", "more": true }instead of every unit: 50 units by default, up to 200 withlimit, sorted by unit ID, with the filtersq,deliveryandrelease. The units in the list have no packages, onlypackage_count;GET .../units/report?unit=<ID>returns one unit with its packages, andGET .../units/statscounts the units, the stale ones and those reporting through bundles. Scripts that read the list must followmore. The Units page searches and filters on the server and has a Load more button. See See what a unit is affected by. - A release names its product and variant.
GET /v1/orgs/{org}/releases/{release}also returnsproduct_id,product(its name) andvariant(the variant’s name). - Wrong query values are refused. A query parameter with a value the route doesn’t take now answers
400withrequest.invalidinstead of being ignored.historyandopentaketrueorfalse;includetakes onlyresolved.
13 November 2026
Section titled “13 November 2026”-
One finding for each CVE. The Vulnerabilities tab of a release now has one row for each CVE, however many advisories report it. The row lists the NVD, OSV, distribution and vendor advisories behind it as chips, shows Sources disagree when one advisory says a component is affected and another says its version is not, and Statements differ when a statement on an advisory differs from the one on the CVE. Details shows the evidence for each component. Assess records a statement on the CVE, which decides for the whole row. Also in is gone: its advisories are chips in the row.
-
The counts drop. Because each CVE counts once, the numbers on the overview (Open findings, Known exploited, Resolved by VEX), on the Vulnerabilities tab and on each release are lower than before. Nothing was resolved by this: before, a CVE that several advisories reported, or that was in several releases, was counted more than once. The hint under Open findings says how many releases they are on. See What the numbers count.
-
One notification for each CVE. Webhooks, email, chat messages and the events feed send one
finding.new,finding.known_exploitedorfinding.resolvedfor each CVE in a release, not one for each advisory. A GitHub advisory that arrives after the NVD record of the same CVE sends nothing, andfinding.resolvedcomes when no advisory reports the CVE any more.release.matchedcounts CVEs. So you receive fewer events. Each finding event has a new field,data.group, with the CVE, the advisories that report it and whether they disagree; the existing fields are unchanged. Emails and chat messages name the CVE. Findings you were told about before stay known, so nothing is sent again. See One event for each CVE. -
Assistants see finding groups.
triageandunassessed_findingsin the MCP server and the graph API now rank one item for each CVE, with the IDs of its advisories, and count CVEs the way the release page does. They take a newconflictparameter that lists only the CVEs where the advisories disagree, andexplain_findingshows the advisories that exclude a component’s version, with the fixed version, asexcludedByedges. An assistant can cite such an edge as evidence for a proposal. -
Go and Python advisories without a CVE count once. A Go advisory (
GO-…) or a Python advisory (PYSEC-…) and the GitHub advisory (GHSA-…) that names it as an alias are now one row, one count and one notification when neither has a CVE. Before, they were two. Affectra reloads its OSV data to learn the aliases, so the rows join during the next day. This sends no notification for findings you were told about.
11 November 2026
Section titled “11 November 2026”Web app 0.1.3 and 0.1.4, API 0.1.4 to 0.1.6.
- Build provenance. Upload the provenance of a GitHub Actions build with your SBOM. The release page’s Firmware tab lists each firmware image, the run that built it and the SBOMs that describe it. See Add build provenance.
- CSAF. Download a release’s VEX statements as a CSAF VEX document, or a CSAF advisory for one vulnerability. An admin sets your organization’s CSAF namespace under Settings. See Export VEX.
- Units linked to releases. Affectra links a unit to the release named in its release file, by product key, variant and version. Units with a version that Affectra does not know are listed as unlinked firmware; a release alias links them. A linked unit gets its release’s VEX statements. See Find affected units.
- Product key and support end. An admin can give each product a key, used in release files, and the last day it gets security updates. See Product key and support end.
- Weaknesses. A finding shows its weakness (CWE), with related attack patterns (CAPEC) and ATT&CK techniques, to help you judge it. See Vulnerability sources.
- How current a release is. A release shows how fresh the vulnerability data behind its findings is, and each finding has a timeline of how it came about. See See how current a release is and Read the findings of a release.
- AI assistants can find a release from a product name and version, propose links between units and releases, and see how fresh the data of an answer is. See MCP server.
- Pages use the full width of the window.
10 November 2026
Section titled “10 November 2026”Web app 0.1.2, API 0.1.3.
- Units are matched against vulnerabilities, from the package URLs that collector 0.1.0 and later report. The Units page marks units whose collector is too old to be matched. See Find affected units.
- Proposals from AI assistants. An assistant can propose VEX statements and package mappings, with its evidence. A member accepts, edits or rejects each one in the app. See Let an agent propose statements.
9 November 2026
Section titled “9 November 2026”Web app 0.1.0 and 0.1.1, API 0.1.0 to 0.1.2. The first release of the hosted service.
- AI assistants sign in as you. An assistant can connect to the MCP server with your own sign-in instead of an API key. See Connect an AI assistant.