Skip to content

← Actionable
Medium, CVSS 4.3amended

oxidize-pdf: NaN/inf bypass in colour content-stream emission causes PDF rejection (DoS)

GHSA-88q9-cmp2-c2vq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (oxidize-pdf 0.5.0; oxidizepdf.net 0.8.0; oxidize-pdf 2.6.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact oxidize-pdf defines Color as a pub enum with public tuple-struct variants Rgb(f64, f64, f64), Gray(f64), and Cmyk(f64, f64, f64, f64). The constructors Color::rgb, Color::gray, and Color::cmyk clamp incoming components to [0.0, 1.0], but because the variants are pub, callers can construct values directly without going through the constructors: rust let safe = Color::rgb(f64::NAN, 0.5, 0.5); // clamps NaN to 0.0 let attack = Color::Rgb(f64::NAN, 0.5, 0.5); // bypasses clamp Color: Copy allows the non-finite value to propagate freely through API surfaces and serialisation. When such a value reaches a content-stream emitter, the writer formats it via format!("{:.3}", v). The Rust standard library renders f64::NAN as "NaN", f64::INFINITY as "inf", and f64::NEGINFINITY as "-inf" — none of which are valid PDF numeric tokens per ISO 32000-1 §7.3.3: ▎ A numeric object shall be represented by one or more decimal digits with an optional sign and a leading, trailing, or embedded PERIOD.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-88q9-cmp2-c2vq

  2. Revision 1 · created ·

    Published from osv record GHSA-88q9-cmp2-c2vq

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-88q9-cmp2-c2vq

Advisory: oxidize-pdf: NaN/inf bypass in colour content-stream emission causes PDF rejection (DoS)
IDs: GHSA-88q9-cmp2-c2vq
Record: https://patchnext.com/advisories/ghsa-88q9-cmp2-c2vq (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: oxidize-pdf 0.5.0; oxidizepdf.net 0.8.0; oxidize-pdf 2.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI oxidize-pdf: affected <= 0.4.3; fixed in 0.5.0
- NuGet oxidizepdf.net: affected <= 0.7.1; fixed in 0.8.0
- crates.io oxidize-pdf: affected <= 2.5.7; fixed in 2.6.0

## Suggested inspection (read-only)
- `python -m pip show oxidize-pdf`: prints the installed version. Run with the environment that serves production active.
- NuGet oxidizepdf.net: check the installed version with your package manager.
- crates.io oxidize-pdf: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on oxidize-pdf, oxidizepdf.net.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-88q9-cmp2-c2vq (OSV record GHSA-88q9-cmp2-c2vq lists affected ranges: crates.io oxidize-pdf >=0 =0 =0 <0.5.0 (fixed))
- Verified: https://github.com/advisories/GHSA-88q9-cmp2-c2vq (GitHub-reviewed advisory GHSA-88q9-cmp2-c2vq lists affected ranges: crates.io oxidize-pdf >=0 =0 =0 <=0.4.3)

Commands are suggestions: review each one before running it.

Loading voting…