Convert-ASN1 memory exhaustion via unchecked length in BER parsing
- Exploited
- No known exploitation
- Fix
- Fixed in 0.37
- Who is exposed
- Not reported
Summary
Convert::ASN1 for Perl, before version 0.37, lets an attacker exhaust memory by sending a crafted BER header that declares an element length of up to 4GB, which the software passes unchecked to sysread and allocates before any data arrives. A single such header can make the reading process allocate that much memory, and if the allocation fails, perl exits with "Out of memory" in a way that eval cannot catch.
Written by a model
Original description
Convert::ASN1 versions before 0.37 for Perl allow memory exhaustion via a declared element length passed unchecked to sysread in asn_read and asn_get.
The length an element declares in its BER header is passed to sysread as the read size. Perl grows the target buffer to that size before reading, so memory is allocated from the declared length, not from the data received. A 6-byte header can declare a length of up to 4GB.
A single header makes the reading process allocate the declared size. Where the allocation fails, perl exits with "Out of memory", which eval cannot catch.
Who should check
Anyone running Convert::ASN1 before 0.37 for Perl that decodes BER/ASN.1 data through asn_read or asn_get.
“CVE-2026-131868: prevent huge allocations in asn_read and asn_get”
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-131868 (Convert::ASN1 versions before 0.37 for Perl allow memory exhaustion via a declared element length passed unchecked to sysread in asn_read…), 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-131868 (entry last updated 2026-11-20):
Affected:
- Convert-ASN1: fixed in 0.37
Fixed versions: 0.37.
Conditions (all must be true for the bug to be hit):
- Affects the asn_read and asn_get functions in Convert::ASN1 before 0.37 for Perl (source: https://github.com/cpan-authors/perl-Convert-ASN1/commit/88bd86b5a3ce3430ebb8b78fe5307f234198bf16.patch)
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-131868 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131868 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/88bd86b5a3ce3430ebb8b78fe5307f234198bf16.patch
- https://metacpan.org/release/TIMLEGGE/Convert-ASN1-0.37/changes
- https://www.cve.org/CVERecord?id=CVE-2026-131868
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-131868
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-131868"}.Affected versions
- Convert-ASN1fixed in 0.37
cve.now Index
- 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
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131868 |
| Record | NVD · CVE-2026-131868 |
| Other links 2 | |
| Patch | GitHub · cpan-authors/perl-Convert-ASN1 · Commit 88bd86b5 |
| Link | metacpan.org · release/TIMLEGGE/Convert-ASN1-0.37/changes |
Questions about CVE-2026-131868
Is CVE-2026-131868 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
What does this mean?
A short crafted ASN.1 element header can make Convert::ASN1 allocate memory up to the length it declares, about 4GB. Where the allocation is refused, perl exits with Out of memory, which eval cannot catch.
Source: github.com, cve.org
Which versions are affected by CVE-2026-131868?
Convert-ASN1: before 0.37.
Source: cve.now feed data
Am I affected, and how do I check?
Convert::ASN1 versions before 0.37 for Perl are affected, specifically through the asn_read and asn_get functions. To check a installed copy, run perl -MConvert::ASN1 -e 'print $Convert::ASN1::VERSION' and compare the result with 0.37.
Source: github.com, cve.org
How do I fix CVE-2026-131868?
Upgrade Convert-ASN1 to version 0.37 or later.
Source: github.com, cve.org
Related
No corrections so far. Something wrong on this page? Report an error.