Skip to main content
Menu
CVEs

CVE

SharpIppNext denial of service via unbounded IPP document buffering

Only affects server-side use of SharpIppServer to parse incoming IPP requests with ReadDocumentStream enabled, which is the default. Fixed in 4.1.0.

CVE-2026-59975EUVD-2026-129189Published Updated Summary written by a model

7.5HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 4.1.0
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Summary

SharpIppNext, a .NET library for Internet Printing Protocol clients and servers, has a flaw in its server-side code that lets a remote attacker cause a denial of service without logging in. The attacker sends an arbitrarily large document body, which is buffered in memory with no size limit until the process runs out of memory and fails.

Original description

SharpIppNext is a .NET Standard library for building Internet Printing Protocol clients and servers. Prior to 4.1.0, server-side SharpIppNext implementations using SharpIppServer.ReceiveRequestAsync or SharpIppServer.ReceiveRawRequestAsync pass incoming data to IppProtocol.ReadIppRequestAsync in SharpIpp/Protocol/IppProtocol.cs, where ReadDocumentStream is enabled by default and the remaining document body is copied with CopyToAsync into a MemoryStream without a size limit. An unauthenticated remote client can send an arbitrarily large IPP document body, exhausting process memory and causing an out-of-memory failure or service termination. Client-only implementations using SharpIppClient are not affected. This issue is fixed in version 4.1.0.

Who should check

Teams running SharpIppNext server-side (SharpIppServer) that accept IPP requests over HTTP, such as print servers or document management systems.

“This vulnerability only affects server-side implementations (using SharpIppServer to parse incoming IPP requests).”

github.com

cve.now Index

48Pcve.now Index 48 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure25/25Default setups, CISA rates it automatable
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active

What to do

  • Check every install: default setups are affected.

  • Upgrade to a fixed version: 4.1.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-59975 (SharpIppNext: Unbounded IPP Document Stream Buffering Leads to Denial of Service), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-59975 (entry last updated 2026-11-18):
Affected:
- danielklecha SharpIppNext: fixed in 4.1.0
Fixed versions: 4.1.0.
Conditions (all must be true for the bug to be hit):
- Server-side use of SharpIppServer (ReceiveRequestAsync or ReceiveRawRequestAsync) to parse incoming IPP requests (source: https://github.com/danielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rrf2)
- ReadDocumentStream is enabled, which is the default setting (source: https://github.com/danielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rrf2)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-59975 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-59975 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/danielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rrf2
- https://github.com/danielklecha/SharpIppNext/commit/30e236e35f415d5172e178c75030cafd53d150fe
- https://github.com/danielklecha/SharpIppNext/commit/fe161eb3d6d114aaf9b2f1e42dea55b097257281
- https://github.com/danielklecha/SharpIppNext/releases/tag/v4.1.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-59975
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-59975"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • danielklecha SharpIppNext

    fixed in 4.1.0

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · danielklecha/SharpIppNext · Advisory GHSA-3h63-w8jq-rrf2
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-59975
RecordNVD · CVE-2026-59975
Other links 3
RepositoryGitHub · danielklecha/SharpIppNext · Commit 30e236e3
RepositoryGitHub · danielklecha/SharpIppNext · Commit fe161eb3
RepositoryGitHub · danielklecha/SharpIppNext · Release v4.1.0

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-59975

Is CVE-2026-59975 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The library buffers the entire IPP document stream in memory without a size limit. A very large request body can exhaust the server process's memory, causing an out-of-memory failure and denial of service.Source: github.com

Which versions are affected by CVE-2026-59975?

SharpIppNext: before 4.1.0.Source: cve.now feed data

Am I affected, and how do I check?

The issue affects server-side use of SharpIppServer through ReceiveRequestAsync or ReceiveRawRequestAsync to parse incoming IPP requests, with ReadDocumentStream enabled, which is the default. To check, look for calls to these methods in the server code and confirm the ReadDocumentStream setting.Source: github.com

How do I fix CVE-2026-59975?

Upgrade SharpIppNext to version 4.1.0 or later.Source: github.com

More CVEs