HighCVE-2026-59975

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

    Published Last modified Sources: EUVD, OSV, Hersteller, CVE.org

    Share

    What is affected, what to do

    Update Danielklecha SharpIppNext to version 4.1.0.

    Affected
    • Danielklecha SharpIppNext lt *..4.1.0
    Fixed in
    • Danielklecha SharpIppNext 4.1.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: EUVD, OSV, Hersteller, CVE.org

    0.6 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 50.7

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    88.04 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.6 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    50.7
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: proof of concept · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 18 November 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-400

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Summary

    SharpIppNext's IppProtocol.ReadIppRequestAsync() unconditionally copies the entire attacker-supplied IPP document payload into an unbounded MemoryStream with no size limit. Because this behavior is enabled by default (ReadDocumentStream = true) and the official server documentation shows HttpContext.Request.Body being passed directly to ReceiveRequestAsync() without authentication, an unauthenticated remote attacker can exhaust the server process's memory by sending an arbitrarily large IPP request body, causing an Out-Of-Memory (OOM) condition and denial of service.

    [!NOTE] This vulnerability only affects server-side implementations (using SharpIppServer to parse incoming IPP requests). It does not affect client-side implementations using SharpIppClient or client-side request construction.

    Details

    The vulnerable sink is in SharpIpp/Protocol/IppProtocol.cs:

    // IppProtocol.cs:39 — enabled by default
    public bool ReadDocumentStream { get; set; } = true;
    
    // IppProtocol.cs:466–470 — no size cap on the copy
    if (ReadDocumentStream)
    {
        message.Document = new MemoryStream();
        await reader.BaseStream.CopyToAsync(message.Document);  // unbounded
        message.Document.Seek(0, SeekOrigin.Begin);
    }
    

    The full call chain from the public API to the vulnerable sink:

    1. docs/Content/Server/index.md:6–11 — Official server example passes context.Request.Body (unauthenticated) to sharpIppServer.ReceiveRequestAsync(inputStream).
    2. SharpIpp/ISharpIppServer.cs:78 — Public API declaration: Task<IIppRequest> ReceiveRequestAsync(Stream stream, ...).
    3. SharpIpp/SharpIppServer.cs:62–67 — ReceiveRequestAsync(Stream) overload delegates to ReceiveRawRequestAsync(stream).
    4. SharpIpp/SharpIppServer.cs:52–58 — ReceiveRawRequestAsync calls _ippProtocol.ReadIppRequestAsync(stream, ...).
    5. SharpIpp/Protocol/IppProtocol.cs:466–470 — ReadIppRequestAsync copies all remaining bytes after the IPP attribute section into a new MemoryStream() with no upper bound.

    The existing validator (IppRequestMessageValidator.ValidateStringLengthLimitsRule, IppRequestMessageValidator.cs:260) only checks IPP attribute string/octet lengths after parsing; it does not constrain the document stream buffered at step 5.

    Dynamic confirmation (Phase 2): a Docker-based PoC server built directly from the v4.0.2 source (commit 185343e) was sent a 100 MB IPP document payload. The server responded docLength=104857600, confirming all 100 MB were buffered into a MemoryStream with no rejection.

    PoC

    1. Build and start the vulnerable server

    # From the repository root (build context: parent of vuln-001/)
    docker build -t sharpipp-dos-poc -f vuln-001/Dockerfile \
      reports/pypiAi_973_danielklecha__SharpIppNext/
    
    docker run --rm -d -p 8631:8631 --name sharpipp-dos-server sharpipp-dos-poc
    

    The PoC server (Program.cs) uses the default SharpIppServer (which uses IppProtocol with ReadDocumentStream = true) and exposes a single unauthenticated POST endpoint:

    using SharpIpp;
    
    var server = new SharpIppServer();
    var app = WebApplication.Create();
    
    app.MapPost("/", async ctx =>
    {
        var req = await server.ReceiveRawRequestAsync(ctx.Request.Body);
        ctx.Response.ContentType = "text/plain";
        await ctx.Response.WriteAsync($"docLength={req.Document?.Length}\n");
    });
    
    app.Run("http://0.0.0.0:8631");
    

    2. Send the crafted IPP request

    python3 vuln-001/poc.py 127.0.0.1 8631 100
    

    The PoC script (poc.py) builds a minimal valid IPP/2.0 Print-Job request (version + operation-id + request-id + operation-attributes-tag + two mandatory attributes + end-of-attributes-tag) followed by an attacker-controlled document body of the requested size, then sends it over HTTP.

    3. Expected output

    [*] Target          : http://127.0.0.1:8631/
    [*] IPP header size : 72 bytes
    [*] Document payload: 100 MB (104,857,600 bytes)
    [*] Total request   : 104,857,672 bytes
    
    [*] Sending request...
    [*] HTTP status : 200
    [*] Response    : docLength=104857600
    
    [PASS] CONFIRMED: server buffered 104,857,600 bytes (100 MB) into MemoryStream with NO size limit.
    [PASS] Vulnerable sink: IppProtocol.cs:469 reader.BaseStream.CopyToAsync(message.Document)
    

    Increasing doc_size_mb (e.g., to 4096 or beyond available RAM) triggers process-level OOM on the target server.

    Recommended fix

    Add a configurable maximum document size and throw client-error-request-entity-too-large when exceeded:

    --- a/SharpIpp/Protocol/IppProtocol.cs
    +++ b/SharpIpp/Protocol/IppProtocol.cs
    +        public long? MaxDocumentStreamBytes { get; set; } = 128L * 1024 * 1024;
    
                 if (ReadDocumentStream)
                 {
                     message.Document = new MemoryStream();
    -                await reader.BaseStream.CopyToAsync(message.Document);
    +                await CopyDocumentStreamAsync(reader.BaseStream, message.Document,
    +                    message, MaxDocumentStreamBytes, cancellationToken).ConfigureAwait(false);
                     message.Document.Seek(0, SeekOrigin.Begin);
                 }
    

    Impact

    This is an unauthenticated network-reachable Denial of Service vulnerability. Any server that follows the official SharpIppNext documentation and passes an HTTP request body to ReceiveRequestAsync() or ReceiveRawRequestAsync() is vulnerable out of the box, because ReadDocumentStream defaults to true and no document size limit exists in the library.

    An attacker with network access to the IPP endpoint can:

    • Send a single HTTP POST request with an arbitrarily large body to exhaust the server process's heap memory.
    • Trigger an OOM kill or OutOfMemoryException, crashing the ASP.NET host process and making the printer/IPP service unavailable.
    • Repeat the attack trivially since no authentication is required and the exploit requires only a standard HTTP client.

    Only consumers of SharpIppNext that expose an IPP server endpoint using SharpIppServer (e.g., print servers, document management systems, and IoT firmware) are affected. Applications acting purely as clients (SharpIppClient) to query printers or submit jobs are not affected.

    Reproduction artifacts

    Dockerfile

    # syntax=docker/dockerfile:1
    # PoC Dockerfile for VULN-001: Unbounded IPP Document Stream Buffering DoS
    #
    # Vulnerability: SharpIppNext v4.0.2 (commit 185343e) buffers the entire
    # attacker-supplied IPP document payload into an unbounded MemoryStream.
    #
    # Affected code (IppProtocol.cs:39, 466-470):
    #   public bool ReadDocumentStream { get; set; } = true;
    #   ...
    #   message.Document = new MemoryStream();
    #   await reader.BaseStream.CopyToAsync(message.Document); // no size limit
    #
    # Build context: the parent directory (pypiAi_973_danielklecha__SharpIppNext/)
    #   docker build -t sharpipp-dos-poc \
    #     -f vuln-001/Dockerfile .
    #
    # Usage:
    #   docker run --rm -d -p 8631:8631 --name sharpipp-dos sharpipp-dos-poc
    #   python3 vuln-001/poc.py
    
    # ---------------------------------------------------------------------------
    # Build stage: compile the PoC server against the vulnerable SharpIpp library
    # ---------------------------------------------------------------------------
    FROM mcr.microsoft.com/dotnet/sdk:10.0 AS build
    
    # Set up the vulnerable library build environment
    WORKDIR /lib
    
    # Create a minimal Directory.Build.props so SharpIpp.csproj can be compiled
    # without TreatWarningsAsErrors (build toolchain compatibility)
    RUN printf '<Project>\n  <PropertyGroup>\n    <Nullable>enable</Nullable>\n    <LangVersion>latest</LangVersion>\n    <NoWarn>$(NoWarn);618;612;NETSDK1138</NoWarn>\n  </PropertyGroup>\n</Project>\n' > Directory.Build.props
    
    # Copy central package versions (required by SharpIpp netstandard2.0 target)
    COPY repo/Directory.Packages.props ./
    
    # Copy the vulnerable SharpIppNext source code (v4.0.2, commit 185343e)
    # IMPORTANT: source is copied unmodified; only the build config above is custom
    COPY 
    

    Source: ENISA EUVD, OSV (Open Source Vulnerabilities), GitHub Security Advisories, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    danielklechaSharpIppNext
    • < 4.1.0
    • 4.1.0
    nugetsharpippnext
    • 1.0.5
    • 2.2.0
    • 4.0.1
    • 1.1.1
    • 2.0.0
    • 2.1.1
    • 1.0.3
    • 2.1.0
    • 2.1.4
    • 2.1.2
    • 1.1.0
    • 1.0.0
    • 1.0.2
    • 4.0.2
    • 2.1.3
    • 2.1.6
    • 3.0.0
    • 1.0.4
    • 1.0.7
    • 4.0.0
    • 1.0.11
    • —
    • 1.0.12
    • 1.0.10
    • 1.0.1
    • 1.0.8
    • 2.1.5
    • 1.0.9
    • 1.0.6
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • 4.1.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    nugetSharpIppNext
    • <= 4.0.2
    • 4.1.0

    Weakness classes (CWE)

    • CWE-400Uncontrolled Resource Consumption

      Class

      The product does not properly control the allocation and maintenance of a limited resource.

      Entry at MITRE CWE-400

    References & sources

    • github.comdanielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rr…euvd, x_refsource_CONFIRM, web
    • github.comdanielklecha/SharpIppNext/commit/30e236e35f415d5172e178c75030ca…euvd, x_refsource_MISC, web
    • github.comdanielklecha/SharpIppNext/commit/fe161eb3d6d114aaf9b2f1e42dea55…euvd, x_refsource_MISC, web
    • github.comdanielklecha/SharpIppNext/releases/tag/v4.1.0euvd, x_refsource_MISC, web
    • NVD (NIST)vuln/detail/CVE-2026-59975advisory, euvd
    • github.comdanielklecha/SharpIppNextpackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedGitHub

      Show 8 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
      Weakness type (CWE)added
      —
      CWE-400
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/59xxx/CVE-2026-59975.json">CVE-2026-59975</a>
      Referenceadded
      —
      https://github.com/danielklecha/SharpIppNext/commit/30e236e35f415d5172e178c75030cafd53d150fe
      Referenceadded
      —
      https://github.com/danielklecha/SharpIppNext/commit/fe161eb3d6d114aaf9b2f1e42dea55b097257281
      Referenceadded
      —
      https://github.com/danielklecha/SharpIppNext/releases/tag/v4.1.0
      Referenceadded
      —
      https://github.com/danielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rrf2

      Source identifier: security-advisories@github.com

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: proof of concept, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/danielklecha/SharpIppNext/security/advisories/GHSA-3h63-w8jq-rrf2
      SSVC assessmentadded
      —
      {"id":"CVE-2026-59975","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-18T20:53:53.666048Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-59975
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-59975"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-59975.svg?lang=en" alt="CVE-2026-59975 – NEOSEC Intel" height="20"></a>