How severe is GHSA-c6rr-7pmc-73wc?

No CVSS score has been assigned to GHSA-c6rr-7pmc-73wc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c6rr-7pmc-73wc?

GHSA-c6rr-7pmc-73wc affects the following packages: @ensdomains/ens-contracts (npm). Ecosystems affected: npm.

How do I fix GHSA-c6rr-7pmc-73wc?

No patched version of @ensdomains/ens-contracts has shipped for GHSA-c6rr-7pmc-73wc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-c6rr-7pmc-73wc in my npm dependencies?

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

How do I mitigate GHSA-c6rr-7pmc-73wc 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 GHSA-c6rr-7pmc-73wc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c6rr-7pmc-73wc can be triaged on real exposure rather than presence alone.

Is GHSA-c6rr-7pmc-73wc actively exploited in the wild?

No public exploit code has been indexed for GHSA-c6rr-7pmc-73wc 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 GHSA-c6rr-7pmc-73wc?

GHSA-c6rr-7pmc-73wc has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th 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 GHSA-c6rr-7pmc-73wc?

GHSA-c6rr-7pmc-73wc is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-c6rr-7pmc-73wc published, and has it been updated?

GHSA-c6rr-7pmc-73wc was published on February 25, 2026 and was last updated on February 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

GHSA-c6rr-7pmc-73wc — @ensdomains/ens-contracts

Fix: ensdomains/ens-contracts@c76c5ad

GHSA-c6rr-7pmc-73wc is a CWE-347 vulnerability in @ensdomains/ens-contracts. No vendor fix is recorded yet; mitigation options are listed below.

ENS DNSSEC Oracle Vulnerable to RSA Signature Forgery via Missing PKCS#1 v1.5 Padding Validation

Also known asCVE-2026-22866

Published

Feb 25, 2026

Updated

Feb 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

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

@ensdomains/ens-contractsnpm

3Kdownloads / week

Description

Impact

The RSASHA256Algorithm and RSASHA1Algorithm contracts fail to validate PKCS#1 v1.5 padding structure when verifying RSA signatures. The contracts only check if the last 32 (or 20) bytes of the decrypted signature match the expected hash. This enables Bleichenbacher's 2006 signature forgery attack against DNS zones using RSA keys with low public exponents (e=3). Two ENS-supported TLDs (.cc and .name) use e=3 for their Key Signing Keys, allowing any domain under these TLDs to be fraudulently claimed on ENS without DNS ownership.

Affected contracts

Contract	Address	Status
RSASHA256Algorithm	0x9D1B5a639597f558bC37Cf81813724076c5C1e96	Vulnerable
RSASHA1Algorithm	0x6ca8624Bc207F043D140125486De0f7E624e37A1	Vulnerable
DNSSECImpl	0x0fc3152971714E5ed7723FAFa650F86A4BaF30C5	Uses vulnerable algorithms
DNSRegistrar	0xB32cB5677a7C971689228EC835800432B339bA2B	Attack entry point

Patches

The bug was reported via Immunefi with possible solutions. The patch was merged at https://github.com/ensdomains/ens-contracts/commit/c76c5ad0dc9de1c966443bd946fafc6351f87587

Workarounds

Deploy the patched contracts
Point DNSSECImpl.setAlgorithm to the deployed contract

Resources

https://github.com/ensdomains/ens-contracts-bug-62248-pr-509

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@ensdomains/ens-contracts`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @ensdomains/ens-contracts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of @ensdomains/ens-contracts has shipped for GHSA-c6rr-7pmc-73wc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 GHSA-c6rr-7pmc-73wc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-c6rr-7pmc-73wc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The `RSASHA256Algorithm` and `RSASHA1Algorithm` contracts fail to validate PKCS#1 v1.5 padding structure when verifying RSA signatures. The contracts only check if the last 32 (or 20) bytes of the decrypted signature match the expected hash. This enables Bleichenbacher's 2006 signature forgery attack against DNS zones using RSA keys with low public exponents (e=3). Two ENS-supported TLDs (.cc and .name) use e=3 for their Key Signing Keys, allowing any domain under these TLDs to be fraudulently claimed on ENS without DNS ownership. Affected contracts Contract | Address | Status --

O3 Security · Impact-Aware SCA

Is GHSA-c6rr-7pmc-73wc in your dependencies?

O3 Security finds GHSA-c6rr-7pmc-73wc 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