Threats / Contributors / GitHub Security Advisories

Registry & coordination contributor

GitHub Security Advisories

cited as evidence in 485 · CNA assigner on 36 (independent) of 485 known-exploited records. Every aggregate on this page is recomputed from the records listed below — each one already cited to its public source.

github.com ↗ · home of the cited advisories

Independent CNA

485

records cited in

deterministic count

finder / reporter credits

CVE.org credits

CVE records catalogued (CNA)

independent

89%

avg modeled exploit prob.

FIRST EPSS, 485/485

29%

ransomware-associated

143 of 485 · CISA flag

Roles across the work

— find / fix / exploit / catalog, computed per record from credit type, the vendor-self-CNA gate, and the linked public exploit catalog

Find

record(s)

Fix

record(s)

Exploit

record(s)

Catalog

record(s)

Each dimension is a count of the listed records where this contributor did that job. A CNA row is fix only when the affected product is the assigner’s own; registries, coordinators, platforms, intel and research houses read as catalog, never fix. Exploit counts records where this contributor is credited as author of a public exploit / detection template in a linked catalog — we link the catalog, never host a payload.

Known for

— recomputed from this contributor’s own records

SurfacesApplication / other (276), Edge / remote-access infra (100), Server / web platform (86), Hypervisor / virtualization (17), Operating system / kernel (6)

WeaknessInjection (167), Path traversal / file (71), Authentication (71), Authorization / access control (47), Web / client (24)

PortfolioApache (35), Oracle (19), Ivanti (19), Synacor (15), VMware (15), Microsoft (14)

Narrative reach

— how far this contributor’s records carry an attacker, front door → lights out

1Front door

468reach this stage

→

2Keys to the kingdom

468reach this stage

→

3Lateral reach

450reach this stage

→

4Data at risk

80reach this stage

→

5Lights out

13reach this stage

Furthest any of these records carries an attacker: 5 · Lights out. 80 of 468 narrative-framed records reach data-at-risk or lights-out. (furthest-position idiom, reused from the landing map; the stage mapping is a model output over cited evidence.)

Recent highlights

— this contributor’s newest known-exploited records

CVE-2026-16232Check Point71%KEV CVE-2026-0770Langflow56%KEV CVE-2026-63030WordPress98%KEV CVE-2026-39808Fortinet90%KEV CVE-2026-15409SonicWall78%RWKEV CVE-2026-56291Balbooa76%KEV

Every record they’re cited in

— all 485, each linked to its cited source

This is the evidence behind every number above. Sorted ransomware-first, then by modeled exploit probability.

Coverage & confidence

— what this profile claims, and what it does not

Established (cited)

Cited in 485 known-exploited records — the list below; every one links to its public source.

Catalogued 36 CVE record(s) as the CNA assigner (from CVE.org).

Coverage gaps — stated, not hidden

This profile is an aggregation: it asserts only what the listed records already cite — no new external claim about the contributor is made.

The TYPE badge and the narrative-stage mapping are editorial (our call), labeled as such, not a sourced fact.