Every change, newest first
Showing changes seen on 2026-07-16. Every day
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | Kind | Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|---|
| Thu 16 Jul 2026· 68 changes | |||||
| 2026-07-16 | Affected range extended | CVE-2026-59840 | fortinetfortios | stated at publication 7.6.2, now states 7.6.3Release branch starts at 7.6.0. | Time to revision 2 days |
| 2026-07-16 | Product added | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50304 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50324 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50355 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50368 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50411 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50647 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50652 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 3.5 and 4.8.1 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-50653 | not named as affected at publication, now names microsoft .net framework 4.8 | Time to revision 2 days | |
| 2026-07-16 | Product added | CVE-2026-4601 | vendor not named snyk | not named as affected at publication, now names org.webjars.npm:jsrsasign | Time to revision 116 days |
| 2026-07-16 | Product added | CVE-2026-10840 | not named as affected at publication, now names red hat openshift builds 1.8.1 | Time to revision 42 days | |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names flps | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names gm32 | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names gms800 | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names gms800 fidor | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names marsic200 | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names marsic280 | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names marsic300 | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names mcs100ft | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names mcs200hw | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names mcs300p | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names mcu eth-service and modbus-tcp module | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names mercem300z | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names mes1b b&b converter | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names sam800 | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names siprocess | Time to revision 672 days |
| 2026-07-16 | Product added | CVE-2024-8751 | SICK AG | not named as affected at publication, now names vicotec320 | Time to revision 672 days |
| 2026-07-16 | Record state changed | CVE-2026-6685 | whole record runZero | stated at publication PUBLISHED, now states REJECTED | Time to revision 15 days |
| 2026-07-16 | Record state changed | CVE-2024-7033 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 483 days |
| 2026-07-16 | Record state changed | CVE-2024-7034 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 483 days |
| 2026-07-16 | Record state changed | CVE-2024-7038 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 645 days |
| 2026-07-16 | Record state changed | CVE-2024-7039 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 483 days |
| 2026-07-16 | Record state changed | CVE-2024-7040 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 483 days |
| 2026-07-16 | Record state changed | CVE-2024-7959 | whole record @huntr_ai | stated at publication PUBLISHED, now states REJECTED | Time to revision 483 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.
What this page cannot see
Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
The units, the refusals, the cut-offs and every source, in full →
Paste your closed CVE tickets and see which of these changes hit them →