How severe is CVE-2025-2792?

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

Which packages are affected by CVE-2025-2792?

CVE-2025-2792 affects the following packages: @mozilla/readability (npm). Ecosystems affected: npm.

How do I fix CVE-2025-2792?

Update @mozilla/readability to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-2792 is resolved across your whole dependency graph.

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

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-2792?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-2792 can be triaged on real exposure rather than presence alone.

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

No public exploit code has been indexed for CVE-2025-2792 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.

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

CVE-2025-2792 was published on March 26, 2025 and was last updated on March 26, 2025. 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-2792 — @mozilla/readability

Fix: mozilla/readability@1c4d63b

CVE-2025-2792 is a security vulnerability in @mozilla/readability. A fix is available for @mozilla/readability — see the affected versions and patch details below.

@mozilla/readability Denial of Service through Regex

Published

Mar 26, 2025

Updated

Mar 26, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 26, 2025 · OSV.dev, 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.

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

@mozilla/readabilitynpm

2.3Mdownloads / week

Description

Specially crafted titles may have caused a regular expression to excessively backtrack and cause a local denial of service.

Additional Details are available at Bugzilla

Credit: DayShift

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@mozilla/readability`	all versions	0.6.0`npm install @mozilla/readability@0.6.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @mozilla/readability, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @mozilla/readability to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-2792 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-2792 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2025-2792. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Specially crafted titles may have caused a regular expression to excessively backtrack and cause a local denial of service. Additional Details are [available at Bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=1948833) Credit: DayShift

O3 Security · Impact-Aware SCA

Is CVE-2025-2792 in your dependencies?

O3 Security finds CVE-2025-2792 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works