UBUNTU-CVE-2026-85644 (CVE-2026-85644)
Vulnerability from osv_ubuntu – Published: 2026-09-29 00:00 – Updated: 2026-09-29 00:00 – Source websiteXS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference. The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union slot that only holds a referent once SvROK(sv) is true, so the guard never validates that it is a reference. For an IV or NV that slot holds the number itself, SvRV() returns the caller's value and SvTYPE() dereferences it at offset 12. This will generally result in a segmentation fault. An application that hands the wrapper a list built from decoded input (for example, from JSON) lets whoever supplies a number in that list choose the address that the interpreter dereferences. An ordinary string's byte 12 is rarely SVt_PVAV so the guard croaks by luck, but an attacker-crafted string carrying 0x0b there passes, and the buffer is then used as an AV head, with AvARRAY taken from bytes 16-23 and its entries pushed onto the Perl stack as live SVs. A simple proof-of-concept uses the zip operator: use Syntax::Operator::Zip 'zip'; my @args = ([1], 2); zip(@args);
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libxs-parse-keyword-perl",
"binary_version": "0.21-1build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "libxs-parse-keyword-perl",
"purl": "pkg:deb/ubuntu/libxs-parse-keyword-perl@0.21-1build1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.21-1",
"0.21-1build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libxs-parse-keyword-perl",
"binary_version": "0.39-1build3"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "libxs-parse-keyword-perl",
"purl": "pkg:deb/ubuntu/libxs-parse-keyword-perl@0.39-1build3?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.38-1",
"0.39-1",
"0.39-1build1",
"0.39-1build2",
"0.39-1build3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libxs-parse-keyword-perl",
"binary_version": "0.49-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "libxs-parse-keyword-perl",
"purl": "pkg:deb/ubuntu/libxs-parse-keyword-perl@0.49-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.48-2",
"0.49-1"
]
}
],
"aliases": [],
"details": "XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference. The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union slot that only holds a referent once SvROK(sv) is true, so the guard never validates that it is a reference. For an IV or NV that slot holds the number itself, SvRV() returns the caller\u0027s value and SvTYPE() dereferences it at offset 12. This will generally result in a segmentation fault. An application that hands the wrapper a list built from decoded input (for example, from JSON) lets whoever supplies a number in that list choose the address that the interpreter dereferences. An ordinary string\u0027s byte 12 is rarely SVt_PVAV so the guard croaks by luck, but an attacker-crafted string carrying 0x0b there passes, and the buffer is then used as an AV head, with AvARRAY taken from bytes 16-23 and its entries pushed onto the Perl stack as live SVs. A simple proof-of-concept uses the zip operator: use Syntax::Operator::Zip \u0027zip\u0027; my @args = ([1], 2); zip(@args);",
"id": "UBUNTU-CVE-2026-85644",
"modified": "2026-09-29T00:00:00Z",
"published": "2026-09-29T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-85644"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85644"
},
{
"type": "REPORT",
"url": "https://lists.security.metacpan.org/cve-announce/msg/43916020/"
},
{
"type": "REPORT",
"url": "https://metacpan.org/release/PEVANS/XS-Parse-Keyword-0.50/diff/PEVANS/XS-Parse-Keyword-0.49/src/infix.c"
},
{
"type": "REPORT",
"url": "https://metacpan.org/release/PEVANS/XS-Parse-Keyword-0.50/changes"
},
{
"type": "REPORT",
"url": "https://metacpan.org/release/PEVANS/XS-Parse-Keyword-0.50/diff/PEVANS/XS-Parse-Keyword-0.49#src/infix.c"
},
{
"type": "REPORT",
"url": "http://www.openwall.com/lists/oss-security/2026/09/28/14"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-85644"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.