CVE-2026-27452
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedASN.1 TypeScript ESM library, including codecs for Basic Encoding Rules (BER) and Distinguished Encoding Rules (DER). In versions 11.0.5 and below, in some cases, decoding an INTEGER could leak the underlying ArrayBuffer. This issue is expected to be fixed in version 11.0.6.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an information disclosure vulnerability in an ASN.1 TypeScript ESM library affecting versions 11.0.5 and below. When decoding INTEGER values using BER/DER codecs, the underlying ArrayBuffer can be leaked in certain cases, potentially exposing sensitive memory contents to attackers who control or influence the ASN.1 data being decoded.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 11.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if the Asn1 Ts library is in useSearch your codebase for imports of 'asn1-ts' or '@asn1ts' package, or check your package-lock.json/package.json for this dependencyAffected if The library is present in dependencies
-
Check installed version of the libraryRun 'npm list asn1-ts' or 'npm list @asn1ts' or inspect node_modules/asn1-ts/package.json to find the version fieldAffected if Version is 11.0.5 or below (any version less than 11.0.6)
-
Verify BER or DER codec usage for INTEGER decodingSearch your codebase for calls to BER or DER decoder functions, particularly those processing INTEGER types, such as 'BER.decode', 'DER.decode', or similar methods from the libraryAffected if Your code uses BER or DER to decode INTEGER values from ASN.1 data
-
Determine source of ASN.1 data being decodedInspect the data source passed to the BER/DER decode functions - check if it originates from external/ network sources, user input, files from untrusted sources, or other potentially attacker-controlled inputsAffected if The ASN.1 data being decoded comes from untrusted or externally controlled sources
You are affected if the Asn1 Ts library version is below 11.0.6 AND your code uses BER/DER codecs to decode INTEGER values from untrusted ASN.1 data sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped11.0.6
Upgrade to version 11.0.6 once released. Until then, avoid processing untrusted ASN.1 INTEGER data with this library and validate all incoming ASN.1 content before decoding.
11.0.6
- Upgrade the @hnie/asn1-ts package to version 11.0.6 or later
- Run npm update @hnie/asn1-ts or npm install @hnie/asn1-ts@latest to apply the fix
- Verify the version was updated by checking package.json or running npm list @hnie/asn1-ts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27452 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27452 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data