CVE-2026-59975 · danielklecha / SharpIppNext
CVE-2026-59975 · Reported 18 Nov 2026
Full advisory details, affected packages, severity context, and original source.
Affected technology
Affected versions and fixes
Version information comes from OSV, NVD, and the CVE vendor record. Each source may describe a different package, release branch, or platform.
danielklecha / SharpIppNext
CVE vendor record- affected: < 4.1.0
Fixed releases / commits: Not explicitly provided by this source. Check the vendor guidance.
Advisory overview
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.
Related references
- https://github.com/danielklecha/SharpIppNext/commit/30e236e35f415d5172e178c75030cafd53d150fe
- https://github.com/danielklecha/SharpIppNext/commit/fe161eb3d6d114aaf9b2f1e42dea55b097257281
- https://github.com/danielklecha/SharpIppNext/releases/tag/v4.1.0
- https://github.com/danielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rrf2
- https://github.com/danielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rrf2
