The last run

The last run was complete. No feed failed, none stopped unexpectedly, and none returned far fewer IDs than the run before it. The counts on this site are still a floor, because only configured feeds are read, but they are comparable to the previous run.

Facts about the run that produced the counts on this site: the snapshot date, when it was built, the code it was built from, and how many rows it published.
Snapshot 2026-11-18
Built 2026-11-18 20:43 UTC (0.0h ago)
Code ba5f59d43cc6
Rows published 1,578

Does this site actually run every six hours?

14 of 28 scheduled runs published in the last 7 days (50.0%), most recently 2026-11-18T07:57:07+00:00.

This site also publishes on every merge to its main branch. Counting those, it published 14 times in the same 7 days, and the longest it went without publishing anything was 15.5 hours. A merge-triggered publish keeps the site fresh but is not evidence that the schedule fired, so it is not counted in the figure above.

Of the 28 ticks expected in that window, 14 published, 0 ran and did not publish, and 14 left no record at all. A tick that leaves no record never started. GitHub delays and drops scheduled workflows under load: on 2026-09-02 the four runs of the day began at 04:35, 11:19, 16:35 and 21:04 against a cron that asks for 00:17, 06:17, 12:17 and 18:17, and six of the 28 expected ticks never fired at all. That is worth seeing and it is not this pipeline failing, which is why the two are no longer added together.

The last figure is a residual rather than a measurement: it is what is left of the expectation after the runs that left a record. Ticks that ran and failed have only been recorded since 2026-09-02, so for the first week after that date this number still carries some of them.

Counted from a ledger appended by the step that actually publishes, so a run that built and failed to deploy is not counted as delivered. This exists because the six-hourly claim had no evidence behind it and was false at least twice: two scheduled ticks on 2026-08-21 produced nothing, with no pushes in the window, and nothing on the site could have told you. Until 2026-09-01 the figure above divided every publish by the scheduled ticks alone and read 164.3%, which could not have told you either.

What moved since the previous run

What moved between this run and the previous one, split into buckets that are deliberately never merged.
BucketRows
New32
Published, verified in the CVE List 14
Rejected under rule 4.5.3.5 0
No longer listed, cause unverified 17
Still open1,546

Only the first of those is good news. A row is counted as published only where the CVE List confirms a published record, taken from the resolution ledger rather than from the difference between two lists.

Rejected is not resolved. Rule 4.5.3.5 requires CNAs to reject unused or unpublished IDs, so rejection is lawful and is the likely end state for the oldest rows here. For anyone consuming the CVE List it is worse than an open RBP: the ID stays cited in advisories and no record is ever coming.

No longer listed means we do not know. A row leaves this list for reasons that have nothing to do with a CNA: a transient API error, a feed that failed or was truncated, a change to the feed set, a raised buffer, or a revised advisory date. None of those are a publication and none are counted as one.

CVE-2026-104796, CVE-2026-105929, CVE-2026-109905, CVE-2026-109906, CVE-2026-109907, CVE-2026-40671, CVE-2026-59964, CVE-2026-61675, CVE-2026-61676, CVE-2026-61677, CVE-2026-61680, CVE-2026-61689, CVE-2026-69138, CVE-2026-69187, CVE-2026-69188, CVE-2026-75506, CVE-2026-76913

Feeds read on this run

Every configured feed and what it returned. A feed that fails is reported here rather than simply yielding fewer rows, because counts are a floor and a silent shrink would read as improvement.

IDs read is how many CVE IDs the feed returned. Rows is how many of the IDs listed on this site that feed referenced, and Only source is how many of those no other feed referenced. The three are very different numbers, and a feed can return tens of thousands of IDs while accounting for none of the list.

A feed that reads from many third-party providers lists each provider beneath it. Capped on any of those rows means this site read only the newest advisories that provider publishes and stopped, which is a limit this site sets rather than anything the provider did. The note column says how many of how many. Those providers hold more than is counted here.

Every configured feed, the state it ended in, how many CVE IDs it returned, how many rows on this site it accounts for, how many of those it is the only source for, and any note about why it stopped. A feed that fans out to third-party providers lists each provider beneath it.
Feed State IDs read Rows Only source Note
acronis OK 160 2 0 160 ids from 264 advisories over 3 page(s)
alas OK 25,922 130 1 25922 ids
alpine OK 5,163 119 0 5163 ids
arch OK 96 0 0 96 ids
broadcom OK 1,383 1 1 1383 ids from 5281 advisories; 3134 of 5281 advisories list no id inline (floor)
certcc OK 354 15 15 354 ids
csaf OK 85,129 698 294 18 providers; 85129 ids; 1 no advisories in scope; see the provider rows below
csaf:advisories.ncsc.nl OK 17,121 17121 ids in scope; caught up across all 1,194 advisories this provider lists
csaf:advisories.stackable.tech OK 15 15 ids in scope; caught up across all 27 advisories this provider lists
csaf:cert-portal.siemens.com OK 3,326 3326 ids in scope; caught up across all 627 advisories this provider lists
csaf:csaf.data.security.nozominetworks.com OK 42 42 ids in scope; caught up across all 126 advisories this provider lists
csaf:intevation.de OK 6 6 ids in scope; caught up across all 6 advisories this provider lists
csaf:psirt.abb.com OK 171 171 ids in scope; caught up across all 87 advisories this provider lists
csaf:psirt.kunbus.com OK 19 19 ids in scope; caught up across all 21 advisories this provider lists
csaf:security.access.redhat.com OK 39,202 39202 ids in scope; caught up across all 59,095 advisories this provider lists
csaf:wid.cert-bund.de OK 70,141 70141 ids in scope; caught up across all 29,274 advisories this provider lists
csaf:www.cisa.gov OK 5,746 5746 ids in scope; caught up across all 2,724 advisories this provider lists
csaf:www.cisco.com OK 1,177 1177 ids in scope; caught up across all 815 advisories this provider lists
csaf:www.huawei.com OK 0 0 ids in scope; caught up across all 0 advisories this provider lists
csaf:www.innomic.com OK 0 0 ids in scope; caught up across all 1 advisories this provider lists
csaf:www.open-xchange.com OK 118 118 ids in scope; caught up across all 22 advisories this provider lists
csaf:www.se.com OK 213 213 ids in scope; caught up across all 150 advisories this provider lists
csaf:www.sick.com OK 175 175 ids in scope; caught up across all 59 advisories this provider lists
csaf:www.suse.com OK 32,928 32928 ids in scope; caught up across all 105,151 advisories this provider lists
csaf:www.trendmicro.com OK 46 46 ids in scope; caught up across all 9 advisories this provider lists
debian OK 37,215 333 25 37215 ids
ghsa OK 19,339 66 0 19339 ids
ghsa-repos OK 14,719 663 558 14719 ids
jvn OK 3,393 5 3 3393 ids
mozilla OK 1,575 0 0 1575 ids
msrc OK 27,120 4 0 27120 ids
osv OK 23,989 198 36 23989 ids
osv:Android OK 2,535 2533 new of 2535 in-scope ids from 10MB
osv:crates.io OK 739 692 new of 739 in-scope ids from 4MB
osv:GitHub Actions OK 42 33 new of 42 in-scope ids from 0MB
osv:Go OK 3,804 3781 new of 3804 in-scope ids from 13MB
osv:Hackage OK 10 8 new of 10 in-scope ids from 0MB
osv:Hex OK 339 337 new of 339 in-scope ids from 1MB
osv:Maven OK 3,088 3014 new of 3088 in-scope ids from 11MB
osv:npm OK 4,564 4525 new of 4564 in-scope ids from 222MB
osv:NuGet OK 650 612 new of 650 in-scope ids from 3MB
osv:opam OK 17 17 new of 17 in-scope ids from 0MB
osv:Packagist OK 3,537 3500 new of 3537 in-scope ids from 11MB
osv:PyPI OK 4,508 4508 new of 4508 in-scope ids from 38MB
osv:RubyGems OK 434 404 new of 434 in-scope ids from 5MB
osv:SwiftURL OK 35 25 new of 35 in-scope ids from 0MB
redhat OK 35,700 132 0 35700 ids
samsung OK 816 43 9 816 ids
ubuntu Capped 3,998 79 0 hit the 200-page cap at 4,000 records of 87,309 (4.6%); read back to 2026-10-18, a 31-day window; the configured window opens 2023-01-01, so most of it was not read
ubuntu:dates OK 25 dated 25 of 49 undated row(s) by name
ubuntu-osv OK 34,499 313 2 34499 ids from 63MB; unpacked 10.21GB of the 16GB ceiling (64%); skipped 806 withdrawn record(s)
zdi OK 4,590 37 22 4590 ids

These feeds publish no dates at all, so their freshness cannot be checked by any threshold. That is not the same as checked and fine: alpine: returns no dated rows; arch: returns no dated rows; debian: returns no dated rows

Standing limitations

These fire on every run, by design. They are not a fault and not a bad day; they are the permanent shape of what the feeds can see, and they are listed apart from the degraded state above because a warning that is always on is not a warning. Recording them as truncation made every single run read as incomplete.

  • ubuntu: hit the 200-page cap at 4,000 records of 87,309 (4.6%); read back to 2026-10-18, a 31-day window; the configured window opens 2023-01-01, so most of it was not read

The consequence worth stating plainly: a paginated advisory API read to a fixed cap is observed over a much shorter window than a distribution tracker read in full, so counts from the two are not directly comparable, and a CNA whose advisories arrive mainly through a capped feed will be under-represented here relative to one carried by a tracker.

How the count itself is built, what it excludes and how far the feeds reach is on the method page. The machine-readable version of everything here is in rbp.json, under degraded, degraded_reasons and feeds.