How severe is CVE-2020-7761?

CVE-2020-7761 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-7761?

CVE-2020-7761 affects the following packages: @absolunet/kafe (npm). Ecosystems affected: npm.

How do I fix CVE-2020-7761?

Update @absolunet/kafe to 3.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7761 is resolved across your whole dependency graph.

How do I detect CVE-2020-7761 in my npm dependencies?

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

How do I mitigate CVE-2020-7761 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-2020-7761 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-7761 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-2020-7761?

CVE-2020-7761 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 75th 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.

When was CVE-2020-7761 published, and has it been updated?

CVE-2020-7761 was published on November 5, 2020 and was last updated on July 9, 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

MEDIUM severity

CVE-2020-7761 — @absolunet/kafe

MEDIUMFix: absolunet/kafe@c644c79

CVE-2020-7761 is a medium-severity (CVSS 5.3) vulnerability in @absolunet/kafe. A fix is available for @absolunet/kafe — see the affected versions and patch details below.

Regular expression denial of service in @absolunet/kafe

Also known asGHSA-hgpf-97c5-74fc

Published

Nov 5, 2020

Updated

Jul 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2020-7761 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@absolunet/kafenpm

60downloads / week

Description

This affects the package @absolunet/kafe before 3.2.10. It allows cause a denial of service when validating crafted invalid emails.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@absolunet/kafe`	all versions	3.2.10`npm install @absolunet/kafe@3.2.10`

Affected Products

1 product · 1 configurations

Application

kafeabsolunet

< 3.2.10

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @absolunet/kafe, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @absolunet/kafe to 3.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-7761 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

This affects the package @absolunet/kafe before 3.2.10. It allows cause a denial of service when validating crafted invalid emails.

O3 Security · Impact-Aware SCA

Is CVE-2020-7761 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works