Vulnerability Advisory Triage: From Alert List to Fix Queue
On November 18, 2026, at 00:17 Singapore time, I sent 15 old package versions to the OSV batch API. The query returned 344 security advisories. After I merged records that share an alias, 242 distinct vulnerabilities rem
On November 18, 2026, at 00:17 Singapore time, I sent 15 old package versions to the OSV batch API. The query returned 344 security advisories. After I merged records that share an alias, 242 distinct vulnerabilities remained. Of these, 163 CVEs carry a high or critical rating, but only 4 appear in the CISA Known Exploited Vulnerabilities (KEV) catalog.
The same night, the EveryInfra github/search_issues capability returned public records from one organization. On November 17, 2026, it dismissed 186 Dependabot alerts in one day, all with the reason not_used. Of those 186 alerts, 148 were in development dependencies only.
Key points
- 15 old dependency versions gave 344 advisories, 242 distinct flaws, and only 4 hits in CISA KEV.
- Alias merge removed 102 duplicates; Pillow 8.1.0 alone had 123 records for 71 flaws.
- KEV added 33 entries from Oct 19 to Nov 13, 2026; 20 had a 3-day deadline, and 20 had EPSS below 0.1.
- One organization dismissed 186 alerts on Nov 17, 2026: 148 in dev scope and 38 in runtime scope.
- Six live data calls cost $0.006209 in total; a daily watch job costs about $0.39 per month.
The main claim of the September version still holds. A vulnerability API gives you candidates. A fix queue needs asset evidence, an owner, and a closing condition. The September version also had a gap. It treated KEV only as a flag for known exploitation and gave no deadlines.
It also missed Binding Operational Directive (BOD) 26-04, which CISA issued on June 10, 2026, three months before that version. BOD 26-04 revokes BOD 22-01 and ties KEV deadlines to internet exposure. This update adds it. The real changes since September come from GitHub. On October 28, 2026, it added reachability analysis to Dependabot. On November 10, 2026, it said it will pause alerts on inactive repositories from December 8. On November 16, 2026, it extended dismissal requests from one week to one year.
Advisories are candidates: how 344 records became 4
A vulnerability database says that some versions of a package are affected. Your team must answer different questions. Is this version in the current build? Where does it run? Can people on the internet reach it? Does your code call the vulnerable function?
Is there a fixed version? Asset evidence connects the two sets of questions. I wanted to measure the gap. I picked 15 common packages, pinned old versions, and queried them in one batch. The OSV API documentation says the batch endpoint accepts package versions and has no rate limit today.
curl -s -X POST https://api.osv.dev/v1/querybatch \
-d '{"queries":[
{"package":{"ecosystem":"PyPI","name":"pillow"},"version":"8.1.0"},
{"package":{"ecosystem":"Maven","name":"org.apache.logging.log4j:log4j-core"},"version":"2.14.1"},
{"package":{"ecosystem":"npm","name":"axios"},"version":"0.21.1"}
]}'
# The batch call returns advisory IDs only.
# Call GET /v1/vulns/{id} for aliases, affected ranges and fixed versions.
The batch endpoint returns IDs only. I fetched all 344 records one by one. Then I grouped records that share any CVE or GHSA alias. The table shows the result for each package. I matched the KEV column against the CISA KEV JSON feed, version 2026.11.13, with 1,781 entries.
| Ecosystem | Package and version | OSV records | After merge | CVEs in KEV |
|---|---|---|---|---|
| PyPI | pillow 8.1.0 | 123 | 71 | CVE-2023-4863 |
| PyPI | django 3.2.0 | 66 | 38 | none |
| Maven | jackson-databind 2.9.8 | 60 | 60 | none |
| npm | axios 0.21.1 | 24 | 24 | none |
| PyPI | urllib3 1.26.4 | 22 | 11 | none |
| PyPI | jinja2 2.11.2 | 10 | 5 | none |
| Maven | log4j-core 2.14.1 | 8 | 8 | CVE-2021-44228, CVE-2021-45046 |
| PyPI | requests 2.25.0 | 8 | 4 | none |
| Maven | spring-web 5.3.17 | 6 | 6 | none |
| npm | lodash 4.17.15 | 5 | 5 | none |
| PyPI | pyyaml 5.3 | 4 | 2 | none |
| npm | jsonwebtoken 8.5.1 | 3 | 3 | none |
| npm | express 4.17.1 | 2 | 2 | none |
| Maven | spring-beans 5.3.17 | 2 | 2 | CVE-2022-22965 |
| npm | minimist 1.2.5 | 1 | 1 | none |
| Total | 15 packages | 344 | 242 | 4 |
The four KEV hits are famous incidents. They are the two Log4Shell IDs, Spring4Shell, and the libwebp heap overflow that ships inside Pillow wheels. Each of them has an EPSS score above 0.996. Of the other 237 CVEs, 25 also have EPSS of 0.1 or more. Most of the rest score low. The median EPSS for all 242 is 0.0166.
EPSS estimates the chance of exploitation in the wild in the next 30 days. I took the November 17, 2026 scores from the FIRST EPSS API. Of 344 advisories, 4 need action tonight, a gap of two orders of magnitude. A product must fill that gap with evidence. It must not push the number 344 to developers as is.
Fixed versions are not the problem here. All 344 records include a fixed version. The problem is how far you must move. I took the fix events from each record and computed the version that clears all alerts for each package. Django must go from 3.2 to 5.2.17. Pillow must go from 8.1.0 to 13.0.0.
urllib3 must go from 1.26 to 2.8.0. jsonwebtoken, Jinja2 and spring-web also cross a major version. minimist and spring-beans need only a patch on the same minor line, and PyYAML needs one minor version. The first group is a project with a schedule and regression tests. The second group is a ten-minute change. If one "to fix" list mixes both, the owner cannot see what closes today.
On November 10, 2026, a developer on r/devops shared a small CLI that sorts alerts by the next action. It uses four groups: fix now with the exact command, blocked by another package, no fix yet, and not in your build (post). It groups by what the owner does next, not by severity.
So the first step is to link each candidate to an asset. Record the repository, component, resolved version, build ID, environment and owner. If you only have default-branch data, limit the claim to that branch. Do not write "production is vulnerable". Lockfiles, build artifacts, images and running instances drift apart.
A lockfile can change while production still runs last month's image. A rebuilt image can bring in a library from its base layer. Write down what you scanned: the lockfile, the image, or the running process. Each can give a different answer. When the deployment state is unknown, the task is "collect asset evidence".
Dependency scope is asset evidence too. GitHub already shows a "Development" label on alerts and lets you filter by scope. Keep that field in the queue.
When sources meet, keep each source before you merge
The merge removed 102 records. Almost all were duplicates. GitHub records a Python vulnerability as a GHSA, and the PyPA database records it again as a PYSEC. Pillow 8.1.0 had 123 records for 71 vulnerabilities. Django 3.2.0 had 66 records for 38.
urllib3 had 22 records for 11. Java and JavaScript packages had almost no duplicates, because OSV has mainly one source for them. The OSV data sources page lists the feeds that OSV collects. The OSV schema uses the aliases and related fields for these links. If a product counts records, Python projects see almost twice the real number of alerts.
Merging removes duplicates, but merges can also go wrong. Keep the raw record from each source. At 00:18 Singapore time on November 18, 2026, I used github/repository_issues on the GitHub advisory database repository. It returned the 30 newest issues and pull requests, all from November 16 and 17, 2026. Of the 30 items, 29 were pull requests, and 26 had the update type "Affected products". In other words, they changed affected ranges.
Three items show the risk. In one issue, the Eclipse Jetty project says it published a reviewed advisory on October 15, 2026, with full affected data. The database instead holds an unreviewed record made from NVD with an empty affected list. One CVE now has two GHSA IDs (advisory-database #11371; the empty record is GHSA-gvw6-wq7h-rwp3).
A pull request says the papaparse advisory has "affected": []. So npm audit, Dependabot and OSV cannot match it to the package (#11370). Another pull request adds WebJars coordinates to a Bootstrap XSS advisory (#11391).
A real response; the teal frame marks an advisory that scanners cannot match. EveryInfra API response, Nov 18, 2026, 00:18:40 SGT
Scanners cannot see this kind of gap. An advisory with no affected list triggers no alert, and the scan shows green. When two IDs point to one vulnerability, one tool may merge on GHSA and another on CVE. Then the same repository shows different alert counts in each tool. The GitHub database also splits records into "reviewed" and "unreviewed".
Dependabot alerts only on reviewed records with package data. The reviewed Jetty advisory did not enter the database. The unreviewed record with an empty list did. A product that reads one source inherits all the blind spots of that source.
At 00:24 Singapore time, I used github/issue_comments on the Jetty issue. The reporter added that this is not a single case. Their own check found a batch of Jetty advisories that appear in the database only as links. The reporter sorted them into three groups by cause.
"Not in this source" or "empty affected list" does not mean "not affected". It means "this source has no usable data for this vulnerability". If you store only the merged value, you cannot explain an old "not affected" decision after the source corrects the range.
NVD also changed its data shape this year. The NVD news page says that from June 17, 2026, the API includes SSVC data from CISA and the CVE "affected" list. About 95% of records got a new lastModified time during that change. From August 26, 2026, change-history entries point to the CVE record on GitHub instead of embedding the affected data. If you sync NVD by timestamp, a new timestamp does not mean a new affected range. Your merge layer must compare field content.
With this model, the normalized object has five field groups. Each group carries a timestamp. When an outside source changes, your team still knows which data version supported an old decision.
| Field group | Content | Why store it separately |
|---|---|---|
| Vulnerability key | Main ID, all aliases, package coordinates, affected ranges | One flaw can have GHSA, PYSEC and CVE IDs |
| Source records | ID per source, first seen, last checked, withdrawn flag | Sources add ranges, change fixed versions, or withdraw |
| Fix data | Fixed versions, vendor mitigations and their conditions | Some fixes exist only in a new major version |
| Asset match | Repository, build ID, image, environment, scope, evidence time | Lockfiles, images and running instances drift |
| Decision | Snapshot of signals, human judgment, owner, state, reason, expiry | Dismissals and accepted risks need review |
Priority: CVSS, EPSS, KEV and reachability answer different questions
The GitHub Dependabot documentation says the default "Most important" sort uses CVSS, dependency scope, and detected calls to vulnerable functions. With reachability analysis on, only "Unreachable" alerts move down. CISA BOD 26-04 sets federal deadlines from four variables. They are public exposure of the asset, KEV status, exploit automation, and partial or total control after exploitation.
The two documents have different goals but the same lesson. One score cannot tell you what to fix first. You need several signals that answer different questions.
| Signal | Publisher | Question it answers | Update rate | Result in this sample |
|---|---|---|---|---|
| CVSS base score | Advisory author, NVD | How bad is the impact after exploitation | On publish or revision | 163 high or critical CVEs |
| EPSS | FIRST | Chance of exploitation in the next 30 days | Daily | 29 at 0.1 or more, median 0.0166 |
| KEV | CISA | Is there reliable proof of exploitation | Most business days | 4 hits |
| SSVC automatable and impact | CISA Vulnrichment | Can attackers automate it, how much control | With the CVE record | Not pulled here |
| Reachability | GitHub, govulncheck and others | Can your code call the vulnerable function | Daily or per scan | Not run here |
| Dependency scope | Lockfile parser | Dev or test only, or in the shipped build | Every build | 148 dev alerts at one org |
These signals do not overlap. I pulled EPSS for the 33 entries that KEV added in the last 30 days, using the November 17, 2026 scores. 20 entries scored below 0.1, and 12 scored below 0.01. The median was 0.0194. Only 5 entries reached 0.5. The reverse also happens.
Log4j 2.14.1 matches CVE-2021-45105 and CVE-2021-44832. Their EPSS scores are 0.99999 and 0.97906, but neither is in KEV. I tested the first case at 01:56 Singapore time on November 18, 2026. For each of the 33 entries, I pulled the EPSS score from the day before KEV added it. Seven entries had no EPSS score yet on that day. Of the other 26, 21 scored below 0.1 the day before, with a median of 0.0060.
By November 17, all 26 scores had gone up. The median reached 0.099, 8 entries crossed 0.1, and 7 rose more than tenfold. Still, 13 stayed below 0.1. The largest jumps were the Collabora Online flaw CVE-2026-110447, added October 23 (0.0123 to 0.733), and the Plex Media Server flaw CVE-2026-96656, added October 20 (0.0040 to 0.198). The two PHP flaws added October 26 already scored 0.9998 and 0.99997 the day before. So EPSS moves up with proof of exploitation, but often not into the high band. Do not use a low EPSS score to argue against KEV. Store EPSS as a daily snapshot, not only the latest value. In a review two weeks later, the team must see whether the rank used 0.004 or 0.198.
The second case shows that KEV lists only entries with reliable proof, not entries that are "likely". If a product averages the two as one score, it fails in both directions.
Reachability is the new signal in 2026. In its October 28, 2026 changelog, GitHub put Dependabot reachability analysis in public preview. CodeQL builds a call graph and looks for a path from your code to the vulnerable functions named in the advisory. Each alert gets one of four verdicts: reachable, potentially reachable, unreachable, or unavailable. The preview supports JavaScript and TypeScript with an npm, Yarn or pnpm lockfile.
It runs only on GitHub Enterprise Cloud. The reachability documentation states two limits. A verdict is a point-in-time result, so do not close an alert only because it is unreachable. A reachable path also does not prove that an attacker can exploit it. Go had a similar tool earlier: govulncheck reports only vulnerabilities that your code calls.
A priority view can list the evidence and the gaps directly. For example: "In the production image; reachability not available for Python; not in KEV; EPSS 0.02; fix exists; upgrade test not started." The owner sees which proof to collect next. In a later review, the team can also see which signal it missed.
CISA already publishes some of these signals. BOD 26-04 says CISA gives answers for KEV status, automation and technical impact for every CVE through the Vulnrichment program. The implementation guidance adds a default. If a CVE is not in KEV and has no automation or impact data, CISA treats it as "not automatable" and "total impact" until someone adds data.
These terms come from the SSVC framework. NVD has carried this data in its API since June 17, 2026. For a product, the rule for missing data must be visible and configurable. Otherwise, vulnerabilities with missing data sink to the bottom of the queue.
KEV deadlines got shorter: 20 of 33 new entries had 3 days
The first version of this article gave no KEV deadlines, so here they are. Under BOD 22-01, the usual deadline was 21 days after the entry was added. The dateAdded and dueDate fields in the KEV JSON show what changed after that. All 31 entries added in October 2025 had 21 days.
From April 2026, no new entry had 21 days. Two windows replaced it: 3 days and 14 days. Of the 33 entries added from October 19 to November 13, 2026 (the last entry in the November 13 release), 20 had 3 days and 13 had 14 days. Entry notes started to cite BOD 26-04 on June 11, 2026.
CISA issued BOD 26-04 on June 10, 2026. It revokes BOD 19-02 and BOD 22-01. Its tightest level is "3 days and forensic triage". The agency must fix or mitigate within 3 days. It must also check whether the asset is already compromised, using the implementation guidance. The guidance gives target times.
Scope the alert within 2 hours of the KEV addition. Collect volatile data before patching, within 2 to 24 hours. Analyze signs of compromise within 24 to 48 hours. Write a triage report and decide on escalation within 48 to 72 hours. When exposure data is missing, CISA uses a fallback. An asset on a public address counts as public, and a network device counts as public.
These rules bind US federal civilian agencies. They still pose a general design problem for advisory products. One KEV entry can mean 3 days on a public device and a later date for the same software on an internal host. The system must know asset exposure before it can compute the deadline. Of the 33 recent entries, 7 have a note that says they affect an open-source component or library.
They are two PHP flaws, Brotli, the Linux kernel, GPUStack, OpenSSH and FreeSWITCH. Most others are VPNs, firewalls, mail gateways and commercial software. A product that scans only application dependencies will see few KEV hits. When a hit comes, the deadline is in days. The alert must skip the daily queue and go straight to the owner.
The seven open-source entries show how fast the deadlines run. All dates are from the KEV JSON, and EPSS is the score of November 17, 2026.
| Date added | CVE | Project | Deadline | EPSS |
|---|---|---|---|---|
| 2026-10-26 | CVE-2026-109618 | PHP | 3 days | 0.99999 |
| 2026-10-26 | CVE-2026-109619 | PHP | 3 days | 0.99999 |
| 2026-10-27 | CVE-2026-111497 | Brotli | 14 days | 0.82641 |
| 2026-10-28 | CVE-2026-46300 | Linux kernel | 3 days | 0.1613 |
| 2026-11-09 | CVE-2026-123158 | OpenSSH | 3 days | 0.189 |
| 2026-11-09 | CVE-2026-116779 | FreeSWITCH | 3 days | 0.02473 |
| 2026-11-09 | CVE-2026-102895 | GPUStack | 3 days | 0.00517 |
GPUStack got a 3-day deadline with an EPSS of 0.00517. A queue that sorts by EPSS alone would put it near the bottom. A queue that reads KEV first puts it at the top.
Teams outside the directive can copy its structure. The UK NCSC vulnerability management guidance asks you to know which vulnerabilities your estate has and where updates fail. NIST SP 800-40 Rev. 4 treats patching as preventive maintenance and a cost of doing business.
Both share one premise with BOD 26-04. You need an asset list and exposure tags before you can compute deadlines. BOD 26-04 asks agencies to tag each externally reachable asset with organization, environment, exposure and asset type. Put those four fields in your asset layer, and you have a minimum model.
News coverage helps you check timing. At 00:18 Singapore time, I used google_news/search for one month of reports on KEV additions. It returned 20 articles, dated from October 21 to November 14, 2026. I compared each one with the KEV dateAdded value. Media reports usually came 1 to 2 days later. KEV added OpenSSH, GPUStack and two other entries on November 9, 2026.
Reports appeared on November 10 and 11. KEV added two PHP flaws on October 26, 2026, and The Record reported them on October 27. With a 3-day window, waiting for the news uses half the time. Subscribe to the KEV JSON or email feed. Use news as background.
A fix queue needs closing conditions
A board with only Open, Dismissed and Fixed cannot show real engineering work. The state model below refines the structure from the first version. It has six main states and three exits. Each state has an entry condition and exit evidence. When the advisory or the asset changes, the alert reopens.
| State | Entry condition | Evidence to exit |
|---|---|---|
| Candidate | A source package range matches a lockfile | Asset links added, or proof of a false match |
| Asset check | Only repository evidence, no build or deploy data | Build ID, image digest, running environment |
| Confirmed | The artifact contains the version, environment known | An owner accepts it and gives a plan |
| Fix planned | Owner, target version and due date exist | A pull request or change ticket |
| Verifying | The change is merged | New lockfile and build no longer match, tests pass, target deployed |
| Closed | Target runs the new build | Reopens on advisory or asset change |
| False match | Wrong package, test fixture only, or retired branch | Evidence link and review date |
| Mitigated | A config or network control blocks the path for now | Source, conditions, expiry, upgrade owner |
| Risk accepted | The business decides not to fix now | Reason, approver, review date |
A version bump does not always close the risk. At 00:15 Singapore time, reddit/search returned a post from October 28, 2026. The GitHub dependency graph does not read Bun's bun.lock. So transitive dependencies in Bun projects never get an alert.
After a move from npm or Yarn to Bun, alerts for the old lockfile get marked as fixed. The vulnerable packages are still in bun.lock (r/javascript post). In the author's small repro, bun audit found 3 advisories and Dependabot raised 1.
At 00:24 I used reddit/comments on that post. One reply points out that the GitHub table of dependency graph ecosystems has no Bun row. The workaround comes from the original poster. Until GitHub reads bun.lock, send the lockfile through the dependency submission API. The poster wrote a GitHub Action for this. This case breaks the "Fixed" state. The alert went away because the scanner lost sight of the package. The risk stayed.
From December 8, another kind of alert will go away. GitHub posted a changelog entry on November 10, 2026. From December 8, 2026, it turns off Dependabot alerts on most repositories with no push in the past year. Existing alerts are archived, not deleted.
Any push restores them. Repositories under an enforced security configuration are not affected. In a vulnerability product, archived alerts need their own state, such as "scanning paused". If the service behind such a repository still runs, the pause itself needs an owner to confirm it.
Dismissals need evidence: what 186 not_used records look like
You need a reason to ignore an alert. At 00:15 Singapore time, I used github/search_issues to look for public issues about Dependabot alerts, dev dependencies and false positives. Sorted by creation time, it returned 30 issues, all created on November 17, 2026. Seven came from seven repositories of one organization.
Each has the title "Dependabot alerts dismissed (2026-11-17)". Each lists the alerts dismissed that day. The total is 186 alerts, all with the reason not_used. By the scope written in each record, 148 were development dependencies and 38 were runtime dependencies.
A real dismissal record; the teal frame marks the reason and the evidence. EveryInfra API response, Nov 18, 2026, 00:15:49 SGT
Each dismissal lists the alert number, the advisory and CVE IDs, the lockfile path and scope, the affected range, and the first fixed version. Then it gives the reason and the evidence. The evidence includes the dependency path from the lockfile, such as devDependencies > [email protected] > [email protected].
It also shows that a code search found no production import, and that the shipped artifact does not include this JavaScript tooling (example record). Each issue closes when it opens, and one label finds them all. It is an auditable dismissal ledger.
The 38 runtime not_used dismissals need stronger proof. Proof for a dev-only dismissal is fairly simple. The lockfile shows that only dev dependencies reach the package, and the artifact does not contain it. A runtime dismissal must prove "not used" with a code search or a call graph.
GitHub's own documentation warns that an unreachable verdict can change with your code or the advisory. A product can set different evidence rules and expiry dates per reason. A dev-only dismissal can last a long time. A runtime not_used can expire after 90 days and trigger a new code search.
Use a fixed set of reason codes. The VEX format (Vulnerability Exploitability eXchange) gives a model. The OpenVEX specification has four statuses: not_affected, affected, fixed and under_investigation. A not_affected status needs one of five justifications. They range from "component not present" to "vulnerable code not in execute path" and "inline mitigations already exist". The spec itself says the last two can be hard to prove.
The CISA minimum requirements for VEX and the CycloneDX VEX format use the same ideas. Map your internal reasons to these codes. Then you can set evidence levels per code. When you publish a VEX statement, you can export your records directly. In the example above, the 148 dev-only records map roughly to "component not present". The 38 runtime records are closer to "vulnerable code not in execute path", which needs much stronger proof.
The same search also returned a counterexample. A Rust repository issue reports a medium serde_with alert in a runtime dependency. Security updates are on, but no fix pull request exists and no issue tracks it. The author writes that "security updates enabled" is only the intake side, and the job is not done until someone triages the alert (CandyriyaMC/candyriya-rs #247). GitHub keeps adding triage tools.
Auto-triage rules can dismiss or snooze alerts by condition. Delegated alert dismissal needs a reviewer to approve each dismissal. The November 16, 2026 changelog extends dismissal requests from one week to one year. With a longer approval window, you must record who asked, who approved, and which evidence version they used.
Send alerts to the owner's queue, not to every inbox
One vulnerability can match dozens of repositories. The fix can be one shared base image, or each service may need its own test. Group alerts before you notify. Create one parent task per shared root cause and one child item per affected asset.
Otherwise, repeated messages create fake work. In the example above, seven repositories each dismissed 9 to 41 alerts on one day. Most came from the same development toolchain. One parent task, "dev toolchain dependencies", can cover all seven.
Filter alerts before they enter the queue, and keep only fix tasks with an owner. Concept illustration for this article
New advisories can also break a release plan. Another issue from the same search comes from a gateway project on a personal account. After the project shipped version 0.2.76, new advisories made its pip-audit and cargo audit jobs fail. The list includes dnspython and opentelemetry-api for Python, plus quinn-proto, quinn-udp, russh, libsqlite3-sys and rustix for Rust. The author fixed main first, shipped 0.2.77, and then merged main into the next branch (issue #474, November 17, 2026; I do not name repositories on personal accounts). No code changed, but the checks went red because the advisory database changed.
My 15 packages show the same effect. Among the 344 OSV records, 44 were published after October 19, 2026, and all 44 belong to Pillow. October 21 alone brought 19 of them, and November 12 brought 2 more. Of the 50 records modified in that period, 45 are also Pillow. This is one package that published a batch of advisories, so do not read it as the growth rate of the whole database. Still, a project pinned to Pillow 8.1.0 got 44 new alerts in one month with no code change. A product should split two types of notice. "A new advisory made an old version red" goes to the dependency owner. "New code added a vulnerability" goes to the author of the change.
A good notice includes the asset, version, environment, priority evidence, fix or mitigation path, missing evidence and a named owner. If nobody owns the asset, show "no receiver". Do not broadcast to the whole engineering team. Keep the urgent channel for events that meet a defined rule, such as "new KEV entry on a public asset". Everything else goes to the daily queue.
Here is an example of a useful urgent notice.
KEV added an OpenSSH flaw on Nov 9, due in 3 days on Nov 12. It matches 2 public bastion hosts, with image digests and deploy times linked. A fix exists. The owner is infrastructure on-call. We still need to check the internal jump host version.
With this notice, the reader knows the task, the proof and the gap.
Show scan failures as a separate state. If a source is down, an SBOM job breaks, or a lockfile format is not supported, a green "no new vulnerabilities" misleads people. The API errors and self-healing guide states the same rule: complete, partial and not run are three different states. The live capability catalog analysis explains why claims, configuration and runtime must stay apart. The failure refund and reconciliation guide is about billing, but its event ledger idea fits here. Each state change must trace back to a cause, an input and a next action.
Watch the advisory sources with public data APIs
Advisory changes are not only visible inside the databases. Pull requests on the advisory repository, dismissal records in project issues, scanner bug reports on Reddit, and news on KEV additions are all public. They all relate directly to your alerts. I pulled each of these with the EveryInfra data API. One key covers GitHub, Reddit and Google News. Every call uses the same shape:
curl -s -X POST https://api.everyinfra.com/api/v1/social \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"platform":"github","action":"repository_issues",
"params":{"url":"https://github.com/github/advisory-database","state":"all","sort":"created"}}'
The fields in each response match the response_fields list in the data catalog. The table lists the six capabilities in this article. I checked each field against the real responses.
| Capability | Use in this article | Key response fields | USD per 1,000 calls |
|---|---|---|---|
github/search_issues |
Find dismissal records and scanner bugs |
title, text, labels, repository, posted_at, state
|
1.917 |
github/repository_issues |
Watch changes to the advisory repository |
is_pull_request, state, merged_at, closed_at
|
0.958 |
github/issue_comments |
Read added evidence under an issue |
text, author_association, posted_at, issue_url
|
0.958 |
reddit/search |
Find developer repros of scanner gaps |
title, text, community, comment_count
|
0.792 |
reddit/comments |
Read replies under a repro post |
text, like_count, posted_at
|
0.792 |
google_news/search |
Check report timing for KEV additions |
title, source, published_at, url
|
0.792 |
Here is the log of the 6 live calls. All three call times are on November 18, 2026, Singapore time. The total charge was $0.006209. Each charged_usd value comes from the billing field of the response.
| Singapore time | Capability | Main parameters | Result | charged_usd |
|---|---|---|---|---|
| 00:15:49 | github/search_issues |
Dependabot alerts, dev dependency, false positive, newest first | 200, 30 items | 0.001917 |
| 00:15:54 | reddit/search |
dependabot alerts noise | 200, 3 items | 0.000792 |
| 00:18:40 | github/repository_issues |
github/advisory-database, all states | 200, 30 items | 0.000958 |
| 00:18:43 | google_news/search |
CISA KEV additions, past month | 200, 20 items | 0.000792 |
| 00:24:38 | github/issue_comments |
advisory-database #11371 | 200, 1 item | 0.000958 |
| 00:24:46 | reddit/comments |
r/javascript bun.lock post | 200, 3 items | 0.000792 |
A daily watch job costs little. Assume 4 github/search_issues calls and 2 github/repository_issues calls per day. Add 2 reddit/search calls and 1 google_news/search call per day, plus 30 comment reads per month. One month costs 120 Γ $0.001917 + 60 Γ $0.000958 + 60 Γ $0.000792 + 30 Γ $0.000792 + 30 Γ $0.000958, which is about $0.39. Failed and empty calls are free. The reddit/search parameter notes say an empty result is refunded.
To ask an AI assistant "Which npm advisory ranges changed today?", connect the remote MCP server:
{
"mcpServers": {
"everyinfra": {
"type": "http",
"url": "https://api.everyinfra.com/mcp",
"headers": { "Authorization": "Bearer ${EVERYINFRA_API_KEY}" }
}
}
}
The tool names start with everyinfra_. The model calls the same github/repository_issues and github/issue_comments capabilities, billed per call. For a first setup, start with the quickstart. These APIs return public discussions and public repository data. They do not replace OSV, NVD or KEV as sources of truth. They tell you earlier where those sources change and where they have gaps.
A minimum version you can build in a week
You do not need a large platform for this. On day one, export an SBOM from your build or parse each repository's lockfiles. Keep four columns: repository, package, resolved version and scope. Mark repositories without build data as "repository evidence only".
On day two, send the list to the OSV batch API and fetch each record. Merge by alias, and store each raw record unchanged. On day three, pull the KEV JSON and the day's EPSS scores. Compute KEV status, deadline and EPSS per vulnerability, and store them as snapshots in the decision layer.
# Merge OSV records into vulnerabilities: records that share any CVE or GHSA ID are one flaw
def merge_by_alias(records):
groups = []
for rec in records:
keys = {rec["id"], *rec.get("aliases", [])}
hit = [g for g in groups if g["keys"] & keys]
merged = {"keys": keys, "sources": [rec]}
for g in hit:
groups.remove(g)
merged["keys"] |= g["keys"]
merged["sources"] += g["sources"] # keep every raw source record
groups.append(merged)
return groups
On day four, add the state model. Create one candidate per merged vulnerability and matched asset. Move it to "asset check" or "confirmed" based on scope and environment. Send KEV hits on public assets straight to the urgent channel. On day five, add the dismissal ledger.
A dismissal needs a reason code, an evidence link and an expiry date, and it reopens on expiry. Add one daily watch job as well. Use github/repository_issues to see if the advisory repository changed your packages. Use github/search_issues and reddit/search to find new known gaps in your scanners. For my 15-package sample, the first cleanup needs human review of 4 KEV hits plus 25 high-EPSS vulnerabilities, 29 in total, not 344 records. After that, people review only what is new or changed each day.
The minimum version needs two more parts. First, "scan did not run" needs its own state. An unsupported lockfile, a query timeout or an empty SBOM must show as yellow in the queue, not as green. Second, compare field content on every outside update.
Re-evaluate assets only when the affected range, fixed version or withdrawn flag changes. If only the timestamp changed, write a log line. The June 17, 2026 NVD change gave about 95% of records a new timestamp. A system that trusts timestamps would have re-evaluated every vulnerability that day.
Pricing: charge for the work you remove, not for alert counts
An early service can cover a few repositories and environments for one engineering team. People on your side can help with false matches, asset ownership and upgrade checks. Price by managed assets, workflow depth and response support. Do not price by the number of vulnerabilities found.
More alerts do not mean more value. The customer pays for the evidence behind each step: why a candidate ranks low, why an alert was dismissed, and why a task closed.
EU rules add a new buyer. An ENISA announcement covers the Cyber Resilience Act (CRA). From September 11, 2026, manufacturers must report actively exploited flaws and severe incidents through one platform. The European Commission page gives three deadlines. Send an early warning within 24 hours of awareness.
Send a full notice within 72 hours. Send a final report within 14 days after a fix is available. The legal text is Regulation (EU) 2024/2847. For companies that sell products with software in the EU, "Do we ship this exploited component, in which version, and when do we fix it?" is now a compliance question with a clock. The asset and decision layers hold the data that the report needs.
Software vendors have one more reason to buy. NIST's Secure Software Development Framework, SP 800-218, lists "identify and confirm vulnerabilities" and "assess, prioritize and remediate vulnerabilities" as basic practices. US federal buyers ask suppliers to attest to it. A fix queue with evidence is both an engineering tool and a record behind that attestation.
Data cost is close to zero here. OSV, KEV and EPSS are free, and the public signal watch in this article costs about $0.39 per month. The main costs are human review and integration. So a monthly fee per managed service fits the cost structure better than a fee per alert. A pilot must show that the weekly human review got shorter, and that each remaining item has evidence and an owner.
In a pilot, track the time from candidate to confirmed, the share of items with no owner, and the duplicate merge rate. Also track time to close, reopen reasons, expired risk acceptances and paused repositories. Do not only show "fewer vulnerabilities found". That number can also fall because scans failed, assets went missing, lockfiles were not read, or someone dismissed alerts in bulk. Base renewal on engineering results.
Do owners understand risk faster? Is there less repeated research? Does each fix leave verifiable evidence? Does the team see coverage gaps in time?
Limits: what this approach does not cover
The sample has only 15 packages, with old versions chosen on purpose. It shows a shape, not any organization's real distribution. KEV favors commercial products and devices, so it understates exploitation of open-source libraries. EPSS is a probability that reacts late to new proof of exploitation.
Do not use it to dismiss a KEV entry. Reachability analysis covers only some languages today. An "unreachable" verdict is a point-in-time result. Dynamic loading, reflection and plugins can hide call paths from static analysis.
Data freshness also has limits. I used the KEV JSON released on November 13, 2026, EPSS scores from November 17, 2026, and OSV results from early November 18, 2026. The three sources differ by a few days. All ratios in this article hold only at that point in time.
Public issues and posts show only teams that choose to write in public. Thirty search results cannot tell you how common a dismissal ledger is. github/search_issues sorted by creation time returns only the newest page, so the sample centers on November 17, 2026. A longer period needs several queries by date.
A dismissal ledger shows what evidence a team used. It does not prove that the decision was right. This article describes a method for turning advisory data into a product. EveryInfra does not offer vulnerability scanning or vulnerability management. Nothing here is a security finding about any specific system.
BOD 26-04 and the CRA apply only within their stated scope. Check the original texts and your own legal advice for your duties. I hid personal usernames and repositories on personal accounts. Repositories owned by organizations appear as they do on GitHub.
Recent changes
- Nov 16, 2026. GitHub extended Dependabot dismissal requests from one week to one year (changelog). Approvals can take longer, so record who approved what and on which evidence.
- Nov 10, 2026. GitHub will pause alerts on repositories with no push for a year, starting December 8 (changelog). Alerts for quiet but running services will be archived. Use an enforced configuration or your own inventory to cover them.
- Oct 28, 2026. Dependabot reachability analysis entered public preview (changelog). JavaScript and TypeScript projects get one more sort signal. Use it to sort, not to close.
- Oct 19 to Nov 13, 2026. KEV added 33 entries, and 20 had a 3-day deadline (KEV catalog). KEV hits need an urgent path. A weekly meeting is too late.
- Nov 16 to 17, 2026. The GitHub advisory repository got 29 pull requests in two days, and 26 changed affected ranges (advisory-database). Advisories keep changing, so store source values and their history.
- Sep 11, 2026. EU CRA reporting duties took effect (ENISA). For products sold in the EU, exploited flaws now have legal reporting deadlines.
FAQ
What is the vulnerability triage process?
In this article's state model, there are six states and three exits. The states are candidate, asset check, confirmed, fix planned, verifying and closed. The exits are false match, mitigated, and risk accepted. For the 3-day level, the BOD 26-04 guidance adds six forensic steps: scope, collect evidence, patch, contain, analyze and decide on escalation.
What is the difference between EPSS, CVSS and KEV?
CVSS rates how bad the impact is after exploitation. EPSS gives the chance of exploitation in the next 30 days. KEV says whether reliable proof of exploitation exists. In this sample, 20 of 33 recent KEV entries had EPSS below 0.1.
Log4j CVE-2021-45105 has EPSS 0.99999 but is not in KEV. Store and show the three separately.
Why are my Dependabot alerts inactive or suddenly gone?
From December 8, 2026, GitHub pauses alerts on repositories with no push for a year. Alerts are archived, and a push restores them. Another cause is a lockfile that the dependency graph cannot read, such as bun.lock. Then alerts vanish because the scanner cannot see the package. Projects that moved from npm can even see old alerts marked as fixed. An Oct 28, 2026 r/javascript post has a minimal repro.
Can I export Dependabot alerts through an API to build my own queue?
Yes. GitHub has a REST API for Dependabot alerts at repository, organization and enterprise level. It also returns reachability verdicts. In the candyriya-rs #247 issue cited above, the author used gh api repos/.../dependabot/alerts to get alert details.
Is it risky to dismiss alerts as not_used?
Dev-only dismissals are easier to prove. The lockfile path shows that only dev dependencies reach the package, and the build does not contain it. A runtime not_used needs a code search or a call graph. GitHub also warns against closing alerts only because they are unreachable.
In the example, 38 of 186 dismissals were runtime. Give these an expiry date and review them. The question comes from a Nov 10, 2026 r/devops post about a tool that sorts alerts by next action (post).
Which vulnerability intelligence feeds should I start with?
KEV has JSON and email feeds. OSV has a batch API by package version. EPSS publishes daily scores through a free API. To watch advisory fixes and scanner gaps, run github/repository_issues and reddit/search daily. This article estimates about $0.39 per month for that watch.
References
- CISA, Known Exploited Vulnerabilities Catalog, ongoing, https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- CISA, KEV JSON feed, version 2026.11.13, Nov 13, 2026, https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
- CISA, BOD 26-04: Prioritizing Security Updates Based on Risk, Jun 10, 2026, https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- CISA, BOD 26-04 Implementation Guidance, updated Aug 25, 2026, https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- CISA, Reducing the Significant Risk of Known Exploited Vulnerabilities, https://www.cisa.gov/known-exploited-vulnerabilities
- CISA, Stakeholder-Specific Vulnerability Categorization (SSVC), https://www.cisa.gov/stakeholder-specific-vulnerability-categorization-ssvc
- CISA, Vulnrichment repository, https://github.com/cisagov/vulnrichment
- CISA, Minimum Requirements for Vulnerability Exploitability eXchange (VEX), https://www.cisa.gov/resources-tools/resources/minimum-requirements-vulnerability-exploitability-exchange-vex
- NIST NVD, News and technical updates (Jun 17 and Aug 26, 2026 entries), https://nvd.nist.gov/general/news
- NIST NVD, CVE-2021-44228 detail, https://nvd.nist.gov/vuln/detail/CVE-2021-44228
- CVE Program, CNA Rules, https://www.cve.org/ResourcesSupport/AllResources/CNARules
- NIST, SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning, Apr 2022, https://csrc.nist.gov/pubs/sp/800/40/r4/final
- NIST, SP 800-218, Secure Software Development Framework, https://csrc.nist.gov/pubs/sp/800/218/final
- UK NCSC, Vulnerability management, https://www.ncsc.gov.uk/collection/vulnerability-management
- European Union, Regulation (EU) 2024/2847 (Cyber Resilience Act), https://eur-lex.europa.eu/eli/reg/2024/2847/oj
- ENISA, The CRA Single Reporting Platform is launched, Sep 11, 2026, https://www.enisa.europa.eu/news/the-cra-single-reporting-platform-is-launched
- European Commission, Cyber Resilience Act: Reporting obligations, https://digital-strategy.ec.europa.eu/en/policies/cra-reporting
- GitHub Docs, Viewing and updating Dependabot alerts, https://docs.github.com/en/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/view-dependabot-alerts
- GitHub Docs, About reachability analysis for Dependabot alerts, https://docs.github.com/code-security/concepts/supply-chain-security/about-reachability-analysis-for-dependabot-alerts
- GitHub Docs, Dependency graph supported package ecosystems, https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/dependency-graph-supported-package-ecosystems
- GitHub Docs, REST API endpoints for dependency submission, https://docs.github.com/en/rest/dependency-graph/dependency-submission
- GitHub Docs, About Dependabot auto-triage rules, https://docs.github.com/en/code-security/dependabot/dependabot-auto-triage-rules/about-dependabot-auto-triage-rules
- GitHub Docs, Enable delegated alert dismissal, https://docs.github.com/code-security/how-tos/manage-security-alerts/manage-dependabot-alerts/enable-delegated-alert-dismissal
- GitHub Changelog, Prioritize Dependabot alerts with reachability analysis, Oct 28, 2026, https://github.blog/changelog/2026-10-28-prioritize-dependabot-alerts-with-reachability-analysis/
- GitHub Changelog, Dependabot alerts will pause on inactive repositories, Nov 10, 2026, https://github.blog/changelog/2026-11-10-dependabot-alerts-will-pause-on-inactive-repositories/
- GitHub Changelog, Dependabot alert dismissal requests now last one year, Nov 16, 2026, https://github.blog/changelog/2026-11-16-dependabot-alert-dismissal-requests-now-last-one-year/
- github/advisory-database, Issue #11371 (Jetty duplicate and empty affected list), Nov 16, 2026, https://github.com/github/advisory-database/issues/11371
- github/advisory-database, PR #11370 (papaparse affected range), Nov 16, 2026, https://github.com/github/advisory-database/pull/11370
- github/advisory-database, PR #11391 (Bootstrap WebJars coordinates), Nov 17, 2026, https://github.com/github/advisory-database/pull/11391
- GitHub Advisory Database, GHSA-gvw6-wq7h-rwp3, https://github.com/advisories/GHSA-gvw6-wq7h-rwp3
- valory-xyz/autonolas-staking-programmes, Issue #171 (dismissal record), Nov 17, 2026, https://github.com/valory-xyz/autonolas-staking-programmes/issues/171
- CandyriyaMC/candyriya-rs, Issue #247 (untracked alert), Nov 17, 2026, https://github.com/CandyriyaMC/candyriya-rs/issues/247
- OpenSSF, OSV Schema, https://github.com/ossf/osv-schema
- Google, OSV-Scanner, https://github.com/google/osv-scanner
- PyPA, pip-audit, https://github.com/pypa/pip-audit
- OpenVEX, Specification, https://github.com/openvex/spec
- npm Docs, npm audit, https://docs.npmjs.com/cli/v11/commands/npm-audit
- OASIS, CSAF Version 2.0, https://docs.oasis-open.org/csaf/csaf/v2.0/csaf-v2.0.html
- EveryInfra, Data catalog (capabilities, parameters, price_usd, response_fields), read Nov 18, 2026, https://api.everyinfra.com/api/v1/social/catalog
- OSV, API documentation, https://google.github.io/osv.dev/api/
- OSV, Data sources, https://google.github.io/osv.dev/data/
- FIRST, Exploit Prediction Scoring System (EPSS), https://www.first.org/epss/
- FIRST, EPSS API, scores of Nov 17, 2026, https://api.first.org/data/v1/epss
- FIRST, CVSS v4.0, https://www.first.org/cvss/v4-0/
- Go, Go Vulnerability Management (govulncheck), https://go.dev/doc/security/vuln/
- CycloneDX, Vulnerability Exploitability eXchange, https://cyclonedx.org/capabilities/vex/
- Hacker News, "Turn Dependabot off" discussion, https://news.ycombinator.com/item?id=47094192
- Reddit r/javascript, Dependabot alerts don't read bun.lock, Oct 28, 2026, https://www.reddit.com/r/javascript/comments/1xhmzbw/dependabot_alerts_dont_read_bunlock_so_transitive/
- Reddit r/devops, CLI that sorts Dependabot alerts by next action, Nov 10, 2026, https://www.reddit.com/r/devops/comments/1xsbl3j/i_made_a_free_cli_that_tells_you_which_dependabot/
- The Record, CISA warns of PHP bug exploitation attempts, Oct 27, 2026, https://therecord.media/php-vulnerabilities-cisa-kev
Originally published on the EveryInfra blog: Vulnerability Advisory Triage: From Alert List to Fix Queue. This article was written with AI assistance; the numbers come from the API calls and sources linked above, and were checked before publishing.
EveryInfra is a pay-per-call data API for AI agents and developers: everyinfra.com.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.


