CVE-2026-130875

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-17. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-127376 (ENISA EUVD) · GHSA-j8j8-frcr-8f56 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

tac_plus-ng before commit d8493e0 contains a stack-based buffer overflow vulnerability that allows clients holding the TACACS+ shared key to overflow a stack buffer due to an operator precedence error in author_pak_looks_bogus() and accounting_pak_looks_bogus(). Attackers can send packets whose argument-length table exceeds the payload, causing eval_args() to read past the packet and memcpy() oversized cmd values into cmdline, crashing the daemon or executing code.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 17, 2026

Last Modified

November 17, 2026

Advisory Details (4)

Auto-updated Nov 17, 2026
🔬 Proof of concept available. Fix referenced — no release confirmed yet. Sources: github, github_commit.
Web page

event-driven-servers/tac_plus-ng/author.c at e20ac825b915492eb4bf5713340a2b0441f01f84 · tacplus-ng/event-driven-servers · GitHub

https://github.com/tacplus-ng/event-driven-servers/blob/e20ac825b915492eb4bf5713340a2b0441f01f84/tac_plus-ng/author.c#L66-L96
Web page

event-driven-servers/tac_plus-ng/packet.c at e20ac825b915492eb4bf5713340a2b0441f01f84 · tacplus-ng/event-driven-servers · GitHub

https://github.com/tacplus-ng/event-driven-servers/blob/e20ac825b915492eb4bf5713340a2b0441f01f84/tac_plus-ng/packet.c#L511-L540
GitHub commit

commit d8493e0d6420 (tacplus-ng/event-driven-servers)

Fix landed in tacplus-ng/event-driven-servers commit d8493e0d6420 — awaiting tagged release

https://github.com/tacplus-ng/event-driven-servers/commit/d8493e0d6420b91737fa34c2cd7bbd365d023b5b
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Stack-Based Buffer Overflow via Operator Precedence Error in tac_plus-ng Authorization and Accounting Length Checks · Advisory · tacplus-ng/event-driven-servers · GitHub

https://github.com/tacplus-ng/event-driven-servers/security/advisories/GHSA-v384-f7x8-f7c7

Vendor Advisories for CVE-2026-130875(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-11-20 01:29 UTCEchelonGraph re-scored
  4. 2026-11-20 01:29 UTCGHSA enrichmentGHSA-j8j8-frcr-8f56 · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-11-19 20:56 UTCOSV refresh
  6. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.5% · 46th percentile
  8. 2026-11-17 23:28 UTCEchelonGraph re-scored
  9. 2026-11-17 23:28 UTCGHSA enrichmentGHSA-j8j8-frcr-8f56 · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-17 22:28 UTCEchelonGraph re-scored
  11. 2026-11-17 22:28 UTCGHSA enrichmentGHSA-j8j8-frcr-8f56 · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-17 21:53 UTCEchelonGraph re-scored
  13. 2026-11-17 21:53 UTCGHSA enrichmentGHSA-j8j8-frcr-8f56 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-17 21:03 UTCENISA EUVD ID recordedEUVD-2026-127376 · Source: ENISA EUVD
  15. 2026-11-17 20:29 UTCEchelonGraph re-scored
  16. 2026-11-17 19:55 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  17. 2026-11-17 19:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-130875?
CVE-2026-130875 is a high-severity vulnerability; its CVE record was published on November 17, 2026. tac_plus-ng before commit d8493e0 contains a stack-based buffer overflow vulnerability that allows clients holding the TACACS+ shared key to overflow a stack buffer due to an operator precedence error in author_pak_looks_bogus() and accounting_pak_looks_bogus(). Attackers can send packets whose…
When was CVE-2026-130875 made public?
CVE-2026-130875 was made public on November 17, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 17, 2026. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-130875 actively exploited?
CVE-2026-130875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-130875?
CVE-2026-130875 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-130875?
A fix for CVE-2026-130875 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-130875 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-130875

Explore →

Is Your Infrastructure Affected by CVE-2026-130875?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.