How severe is CVE-2025-32029?

No CVSS score has been assigned to CVE-2025-32029 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-32029?

CVE-2025-32029 affects the following packages: @apeleghq/asn1-der (npm). Ecosystems affected: npm.

How do I fix CVE-2025-32029?

Update @apeleghq/asn1-der to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32029 is resolved across your whole dependency graph.

How do I detect CVE-2025-32029 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apeleghq/asn1-der, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-32029 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2025-32029 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-32029 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-32029?

CVE-2025-32029 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 15th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-32029?

CVE-2025-32029 is classified as CWE-835 (CWE-835), CWE-1335 (CWE-1335). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-32029 published, and has it been updated?

CVE-2025-32029 was published on April 7, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2025-32029 — @apeleghq/asn1-der

Fix: ApelegHQ/ts-asn1-der@b2bc903

CVE-2025-32029 is a CWE-835 vulnerability in @apeleghq/asn1-der. A fix is available for @apeleghq/asn1-der — see the affected versions and patch details below.

ts-asn1-der has Incorrect DER Encoding of Numbers Leading to Denial of Service and Incorrect Value Representation

Also known asGHSA-p4qw-7j9g-5h53

Published

Apr 7, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-32029.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs15th percentile — riskier than 15% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@apeleghq/asn1-dernpm

44downloads / week

Description

Impact

Incorrect number DER encoding can lead to denial on service for absolute values in the range 2**31 -- 2**32 - 1. The arithmetic in the numBitLen didn't take into account that values in this range could result in a negative result upon applying the >> operator, leading to an infinite loop.

In addition, number encoding had a few other issues that resulted it in it not encoding values correctly.

Patches

The issue is patched in version 1.0.4. Users are recommended to upgrade as soon as possible.

Workarounds

If upgrading is not an option, the issue can be mitigated by validating inputs to Asn1Integer to ensure that they are not smaller than -2**31 + 1 and no larger than 2**31 - 1. Although Asn1Integer supports bigint inputs, some additional implementation issues make using bigint as a mitigation inviable, as it will result in incorrect values.

If upgrading is not an option and range checks are impractical or undesirable, input to Asn1Integer can be provided as a buffer to be used directly. Note that this requires computing the correct DER encoding externally.

References

N/A

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@apeleghq/asn1-der`	all versions	1.0.4`npm install @apeleghq/asn1-der@1.0.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apeleghq/asn1-der, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @apeleghq/asn1-der to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32029 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact Incorrect `number` DER encoding can lead to denial on service for absolute values in the range `2**31` -- `2**32 - 1`. The arithmetic in the `numBitLen` didn't take into account that values in this range could result in a negative result upon applying the `>>` operator, leading to an infinite loop. In addition, `number` encoding had a few other issues that resulted it in it not encoding values correctly. ### Patches The issue is patched in version `1.0.4`. Users are recommended to upgrade as soon as possible. ### Workarounds If upgrading is not an option, the issue can be miti

O3 Security · Impact-Aware SCA

Is CVE-2025-32029 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works