CVE-2026-75883

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The code in pppd that formats a response to a PEAP Request packet in peap_response() copies an entire TLS record of up to 16384 bytes into the fixed global buffer outpacket_buf without checking the available space and without implementing outgoing PEAP fragmentation. Thus a pppd process connecting to a server which requests PEAP authentication can be induced to corrupt global static data following the outpacket_buf array, most likely causing incorrect behavior or a crash.

CVSS v3
6.8
EG Score
6.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 18, 2026
Patch available. Sources: github.
github Patch Available

PPPD buffer overflow in PEAP response code · Advisory · ppp-project/ppp · GitHub

Affected: 2.5.4. PEAP support can be disabled by using the

https://github.com/ppp-project/ppp/security/advisories/GHSA-rwr9-4vx8-vc35

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-19 17:34 UTCEG score recompute
  3. 2026-09-18 16:26 UTCEG score recompute
  4. 2026-09-18 15:36 UTCEG score recompute
  5. 2026-09-18 15:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-75883?
CVE-2026-75883 is a medium vulnerability published on September 18, 2026. The code in pppd that formats a response to a PEAP Request packet in peapresponse() copies an entire TLS record of up to 16384 bytes into the fixed global buffer outpacketbuf without checking the available space and without implementing outgoing PEAP fragmentation. Thus a pppd process connecting to…
When was CVE-2026-75883 disclosed?
CVE-2026-75883 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75883 actively exploited?
CVE-2026-75883 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.5% of all scored CVEs.
What is the CVSS score of CVE-2026-75883?
CVE-2026-75883 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-75883?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75883, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-75883?

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