CVE-2026-59975
Received Received - Intake

Memory Exhaustion in SharpIppNext IPP Server

Vulnerability report for CVE-2026-59975, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 3 associated CPEs

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Denial of Service (DoS) vulnerability in SharpIppNext, a .NET library for Internet Printing Protocol (IPP) communication. Server-side implementations using SharpIppServer.ReceiveRequestAsync or SharpIppServer.ReceiveRawRequestAsync pass incoming data to IppProtocol.ReadIppRequestAsync, which copies the entire document body into a MemoryStream without size limits. An unauthenticated attacker can send a large IPP document body, exhausting server memory and causing an out-of-memory failure or service termination.

Detection Guidance

To detect this vulnerability, monitor for unusually large IPP document payloads being processed by SharpIppNext servers. Check for memory exhaustion events or crashes in server logs. Use network traffic analysis tools like Wireshark to inspect HTTP POST requests to IPP endpoints for abnormally large request bodies exceeding typical document sizes.

Impact Analysis

If you run a server using SharpIppNext versions before 4.1.0, an attacker could send a single large request to crash your server by consuming all available memory. This leads to service unavailability, potential downtime, and disruption of IPP printing services. Client-only applications are not affected.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by enabling denial-of-service attacks that disrupt service availability. GDPR requires maintaining system availability, and HIPAA mandates safeguards against unauthorized disruptions. The out-of-memory failure caused by unbounded document buffering may violate these requirements.

Mitigation Strategies

Upgrade to SharpIppNext version 4.1.0 or later to apply the fix. If upgrading is not immediately possible, implement a network-level solution to block or limit the size of IPP document payloads. Configure a reverse proxy or firewall to reject HTTP POST requests with bodies larger than 128 MB to the IPP endpoint.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-59975. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...