Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5amended

ONNX has Null Pointer Dereference in Upsample Version Converter Adapter (Zero Inputs)

CVE-2026-44512GHSA-hwpq-hmq9-wj77

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (onnx 1.22.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.

Add to your agent

Affected packages

  • PyPI onnx

    Affected
    >= 1.9.0, < 1.22.0
    Fixed in
    1.22.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.5 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-44512: 0.19% estimated exploitation activity in the next 30 days; percentile 9.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Null pointer dereference (SIGSEGV) in Upsample67::adaptupsample67() (onnx/versionconverter/adapters/upsample67.h:31) when convertversion() processes a model with an Upsample node that has zero inputs. The adapter accesses node-inputs()[0]-sizes() without checking input count. 107-byte PoC crashes on Release build. This is the same class of bug as the Cast adapter advisory (separate report) but in a different adapter, different file, and different operator. Details The Upsample 6→7 adapter validates attributes but not inputs: The PoC has an Upsample node at opset 6 with the required widthscale and heightscale attributes but zero inputs. The attribute assertions pass, then node-inputs()[0] on an empty ArrayRef: - Release builds (NDEBUG): bounds-check assertion compiled out → reads garbage pointer → SIGSEGV - Debug builds: assert(Index < Length) at arrayref.h:159 → SIGABRT An Upsample node with zero inputs passes graphProtoToGraph() because the import code only resolves input…

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

    Amended from ghsa record GHSA-hwpq-hmq9-wj77

  2. Revision 1 · created ·

    Published from osv record GHSA-hwpq-hmq9-wj77

Agent brief

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

# Patch Next advisory brief: CVE-2026-44512

Advisory: ONNX has Null Pointer Dereference in Upsample Version Converter Adapter (Zero Inputs)
IDs: CVE-2026-44512, GHSA-hwpq-hmq9-wj77
Record: https://patchnext.com/advisories/cve-2026-44512 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: onnx 1.22.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI onnx: affected >= 1.9.0, < 1.22.0; fixed in 1.22.0

## Suggested inspection (read-only)
- `python -m pip show onnx`: prints the installed version. Run with the environment that serves production active.

## 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 onnx.
- 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-hwpq-hmq9-wj77 (OSV record GHSA-hwpq-hmq9-wj77 lists affected ranges: PyPI onnx >=1.9.0 <1.22.0 (fixed))
- Verified: https://github.com/advisories/GHSA-hwpq-hmq9-wj77 (GitHub-reviewed advisory GHSA-hwpq-hmq9-wj77 lists affected ranges: PyPI onnx >=1.9.0 <1.22.0)

Commands are suggestions: review each one before running it.

Loading voting…