Nixpkgs security tracker

Published

Permalink CVE-2026-75883

6.8 MEDIUM

CVSS version (CVSS): 3.1
Attack Vector (AV): Adjacent (A)
Attack Complexity (AC): High (H)
Privileges Required (PR): None (N)
User Interaction (UI): None (N)
Scope (S): Unchanged (U)
Confidentiality (C): High (H)
Integrity (I): High (H)
Availability (A): None (N)
Modified Attack Vector (MAV): Adjacent (A)
Modified Attack Complexity (MAC): High (H)
Modified Privileges Required (MPR): None (N)
Modified User Interaction (MUI): None (N)
Modified Confidentiality (MC): High (H)
Modified Scope (MS): Unchanged (U)
Modified Integrity (MI): High (H)
Modified Availability (MA): None (N)

updated 10 hours ago by @LeSuisse Activity log

Created suggestion 18 hours ago
@Scrumplex ignored
9 packages
- luppp
- rpPPPoE
- rp-pppoe
- perlPackages.DevelPPPort
- python313Packages.xmpppy
- python314Packages.xmpppy
- perl5Packages.DevelPPPort
- perlPackages.ModuleBuildPluggablePPPort
- perl5Packages.ModuleBuildPluggablePPPort
12 hours ago
@Scrumplex accepted 12 hours ago
@LeSuisse published on GitHub 10 hours ago

PPPD buffer overflow in PEAP response code

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.