Vendor security team contributor

Cisco

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

cisco.com ↗ · home of the cited advisories

102

records cited in

deterministic count

finder / reporter credits

CVE.org credits

CVE records catalogued (CNA)

assigner

36%

avg modeled exploit prob.

FIRST EPSS, 102/102

ransomware-associated

7 of 102 · 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

SurfacesOperating system / kernel (46), Application / other (36), Edge / remote-access infra (20)

WeaknessMemory safety (20), Injection (14), Resource / availability (13), Authentication (7), Authorization / access control (6)

PortfolioCisco (99), GNU (1), Erlang (1), Splunk (1)

Narrative reach

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

1Front door

92reach this stage

→

2Keys to the kingdom

90reach this stage

→

3Lateral reach

67reach this stage

→

4Data at risk

12reach this stage

→

5Lights out

1reach this stage

Furthest any of these records carries an attacker: 5 · Lights out. 12 of 92 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-76460Cisco14%KEV CVE-2026-76461Cisco2%KEV CVE-2026-20079Cisco88%KEV CVE-2026-20349Cisco1%KEV CVE-2026-20316Cisco35%RWKEV CVE-2008-4128Cisco34%KEV

Every record they’re cited in

— all 102, each linked to its cited source

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

CVE-2020-3580Cisco86%RWKEV CVE-2020-3259Cisco72%RWKEV CVE-2026-20131Cisco43%RWKEV CVE-2026-20316Cisco35%RWKEV CVE-2020-3153Cisco28%RWKEV CVE-2023-20269Cisco25%RWKEV CVE-2020-3433Cisco10%RWKEV CVE-2021-1498Cisco100%KEV CVE-2020-3452Cisco100%KEV CVE-2021-1497Cisco100%KEV CVE-2018-0296Cisco100%KEV CVE-2019-1653Cisco100%KEV CVE-2014-6278GNU100%KEV CVE-2023-20198Cisco100%KEV CVE-2018-0171Cisco99%KEV CVE-2017-3881Cisco99%KEV CVE-2025-32433Erlang99%KEV CVE-2025-20281Cisco97%KEV CVE-2024-20439Cisco97%KEV CVE-2026-20253Splunk97%KEV CVE-2019-1652Cisco96%KEV CVE-2026-20182Cisco92%KEV CVE-2023-20273Cisco90%KEV CVE-2026-20127Cisco88%KEV CVE-2026-20230Cisco88%KEV CVE-2026-20079Cisco88%KEV CVE-2016-6415Cisco88%KEV CVE-2016-6366Cisco88%KEV CVE-2025-20362Cisco87%KEV CVE-2020-3161Cisco84%KEV CVE-2022-20699Cisco72%KEV CVE-2024-20353Cisco71%KEV CVE-2025-20333Cisco71%KEV CVE-2017-6736Cisco70%KEV CVE-2025-20337Cisco68%KEV CVE-2018-0125Cisco55%KEV CVE-2023-20118Cisco54%KEV CVE-2017-6737Cisco45%KEV CVE-2015-0666Cisco40%KEV CVE-2025-20352Cisco39%KEV CVE-2008-4128Cisco34%KEV CVE-2025-20393Cisco32%KEV CVE-2026-20133Cisco32%KEV CVE-2026-20262Cisco28%KEV CVE-2026-20245Cisco25%KEV CVE-2026-20122Cisco25%KEV CVE-2016-6367Cisco23%KEV CVE-2017-6742Cisco21%KEV CVE-2024-20359Cisco19%KEV CVE-2014-2120Cisco19%KEV CVE-2018-0147Cisco18%KEV CVE-2024-20481Cisco16%KEV CVE-2022-20708Cisco15%KEV CVE-2018-0151Cisco14%KEV CVE-2026-76460Cisco14%KEV CVE-2017-12240Cisco14%KEV CVE-2022-20775Cisco12%KEV CVE-2020-3118Cisco12%KEV CVE-2022-20821Cisco11%KEV CVE-2017-6740Cisco11%KEV CVE-2017-6738Cisco11%KEV CVE-2017-6739Cisco11%KEV CVE-2017-6743Cisco11%KEV CVE-2022-20701Cisco10%KEV CVE-2022-20703Cisco9%KEV CVE-2018-0156Cisco9%KEV CVE-2018-0172Cisco8%KEV CVE-2026-20128Cisco8%KEV CVE-2018-0155Cisco8%KEV CVE-2018-0173Cisco8%KEV CVE-2018-0174Cisco8%KEV CVE-2017-6744Cisco7%KEV CVE-2018-0158Cisco7%KEV CVE-2017-12231Cisco7%KEV CVE-2017-12233Cisco7%KEV CVE-2017-12234Cisco7%KEV CVE-2017-12235Cisco7%KEV CVE-2017-12237Cisco7%KEV CVE-2018-0154Cisco7%KEV CVE-2018-0159Cisco7%KEV CVE-2017-6627Cisco6%KEV CVE-2010-3035Cisco6%KEV CVE-2022-20700Cisco6%KEV CVE-2019-15271Cisco5%KEV CVE-2017-12319Cisco5%KEV CVE-2018-0179Cisco5%KEV CVE-2018-0180Cisco5%KEV CVE-2004-1464Cisco5%KEV CVE-2026-20045Cisco5%KEV CVE-2024-20399Cisco4%KEV CVE-2018-0161Cisco4%KEV CVE-2020-3566Cisco4%KEV CVE-2018-0175Cisco3%KEV CVE-2018-0167Cisco3%KEV CVE-2020-3569Cisco3%KEV CVE-2009-2055Cisco3%KEV CVE-2023-20109Cisco2%KEV CVE-2017-12232Cisco2%KEV CVE-2017-6663Cisco2%KEV CVE-2026-76461Cisco2%KEV CVE-2017-12238Cisco2%KEV CVE-2026-20349Cisco1%KEV

Coverage & confidence

— what this profile claims, and what it does not

Established (cited)

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

Catalogued 98 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.