Skip to main content
VulnerabilityPublished

CVE-2026-59975: SharpIppNext · Unbounded IPP Document Stream Buffering Leads to Denial of Service

Affects SharpIppNextSource GCVE Database

0
Compare
Authoritative record:CVE-2026-59975· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.1.0 soon.

Data as of 19 Nov 2026, 21:06 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 4.1.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade SharpIppNext to 4.1.0.

Affected software

ProductAffectedFixed in
NuGetSharpIppNextAffected
  • <4.1.0
Fixed in
  • 4.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in SharpIppNext version 4.1.0 that adds a configurable maximum document stream size to prevent unbounded memory allocation. Users should upgrade to version 4.1.0 or later. Until patched, administrators should consider mitigating exposure by restricting access to the IPP server endpoint or implementing upstream request size limits. No other vendor advisories indicate alternative mitigations or that the issue is already mitigated.

Description

SharpIppNext server-side implementations are vulnerable to a denial of service (DoS) due to unbounded buffering of IPP document streams. The method ReadIppRequestAsync() copies the entire attacker-supplied IPP document payload into a MemoryStream without size limits, allowing an unauthenticated remote attacker to exhaust server memory by sending large IPP requests. This affects versions prior to 4.1.0 and is fixed in 4.1.0.

References

Community reviews

Loading reviews…