Skip to main content
Menu
CVEs

Convert-ASN1 CPU exhaustion in binary REAL decoding

CVE-2026-126576EUVD-2026-130801GHSA-6J49-WRH8-CRCCPublished , updated

7.5HighCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 0.37
Who is exposed
Not reported

Summary

Earlier releases of Convert::ASN1 for Perl, before the fixed version, do not check the exponent length when decoding binary REAL values. An attacker who controls the data being decoded can exhaust CPU by sending a list of such values, and the decoded results can also be built from bytes outside each element.

Written by a model

Original description

Convert::ASN1 versions before 0.37 for Perl allow CPU exhaustion via unchecked exponent length in binary REAL decoding.

Binary REAL decoding never bounds-checks the exponent length against the available content. For a minimal one-byte binary REAL, the exponent byte is read from outside the element, making the mantissa length -1. Perl reads a negative length as an offset from the end of the string, so the mantissa is nearly all of the input that follows the element. The long-form exponent path also omits the extra length octet when sizing the mantissa.

An attacker who controls the decoded data can exhaust CPU with a list of such values, as each mantissa loop iterates over the remaining input. The decoded values are also computed from bytes outside each element.

What to do

Upgrade to a fixed version: 0.37.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126576 (Convert::ASN1 versions before 0.37 for Perl allow CPU exhaustion via unchecked exponent length in binary REAL decoding), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126576 (entry last updated 2026-11-20):
Affected:
- Convert-ASN1: fixed in 0.37
Fixed versions: 0.37.
Vendor patches: 6158dbb33cc3d248a95b4ab4948a135e18141b51 (source: https://www.cve.org/CVERecord?id=CVE-2026-126576). Check each asset for these patch ids, not only its version.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126576 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126576 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/cpan-authors/perl-Convert-ASN1/commit/6158dbb33cc3d248a95b4ab4948a135e18141b51.patch
- https://github.com/cpan-authors/perl-Convert-ASN1/issues
- https://metacpan.org/release/TIMLEGGE/Convert-ASN1-0.37/changes
- https://www.cve.org/CVERecord?id=CVE-2026-126576
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126576
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126576"}.

Affected versions

cve.now Index

28Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 5

Questions about CVE-2026-126576

Is CVE-2026-126576 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-126576?

Convert-ASN1: before 0.37.

Source: cve.now feed data

How do I fix CVE-2026-126576?

Upgrade to Convert-ASN1 0.37 or later. The fix is also available as patch commit 6158dbb33cc3d248a95b4ab4948a135e18141b51.

Source: cve.org

No corrections so far. Something wrong on this page? Report an error.