Skip to content
patchdrift.
snapshot 2026-09-07

All changesjpcertas of 2026-09-07

CVE-2024-23910

elecom co.,ltd.wrc-1167gst2cve.org →this looks wrong →

Record history

4 dated edit events

  1. Published

    • 6 products named later, not at publication
    36 days between events

  2. Products addedSource 7dd704c — commit 7dd704c159a6 in the CVE catalog

    • not namedwrc-g01-w, wrc-x3200gst3-b
    69 days between events

  3. Products addedSource a20b117 — commit a20b117b7b72 in the CVE catalog

    • not namedwmc-x1800gst-b, wsc-x1800gs-b
    89 days between events

  4. Product addedSource ef27189 — commit ef27189b3260 in the CVE catalog

    • not namedwrc-2533gst2
    78 days between events

  5. Product addedSource dc4c66c — commit dc4c66c02b74 in the CVE catalog

    • not namedwrc-1167gst2
    650 days to snapshot

  6. Snapshot

    Source record: View on CVE.org ↗

Check your tickets

Add your patched version to compare it with the recorded boundary.

One per line · up to 500 IDs

Versions & supported formats

Add a patched version beside a CVE to compare it. GHSA versions are not compared. Product names are also supported. Results include a watchlist link, RSS and JSON.

Privacy & sharingData & methodology

Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. The full recipe →

Data coverage & methodology

CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.

Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.

Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.

The GitHub Advisory Database was read and carries no changed advisory naming CVE-2024-23910. An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.

How every one of these figures is measured, in full →

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.

Shipped snapshot computed 2026-09-07 from catalog commit ed5547afbae2. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.