PPPD buffer overflow in PEAP response code

Answer in brief

CVE-2026-75883 records a Unknown severity vulnerability in PPPD buffer overflow in PEAP response code. The current sources do not mark it as known exploited. The current feed maps PPP Project/ppp (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 18, 2026Updated Sep 18, 2026Source checked Sep 18, 2026First seen by HOL Sep 18, 2026Material review Sep 18, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps PPP Project/ppp (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
PPP Project/pppgeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for PPP Project/ppp.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 18, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.