GHSA-rrxv-q8m4-wch3 is a medium-severity (CVSS 4.9) remote code execution vulnerability in @ensdomains/ens-contracts. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @ensdomains/ens-contracts — see the affected versions and patch details below.
.eth registrar controller can shorten the duration of registered names
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-rrxv-q8m4-wch3.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-rrxv-q8m4-wch3 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
@ensdomains/ens-contractsnpmDescription
Description
According to the documentation, controllers are allowed to register new domains and extend the expiry of existing domains, but they cannot change the ownership or reduce the expiration time of existing domains. However, a preliminary analysis suggests that an attacker-controlled controller may be able to reduce the expiration time of existing domains due to an integer overflow in the renew function.
The vulnerability resides in the following GitHub repository: https://github.com/ensdomains/ens-contracts/blob/master/contracts/ethregistrar/BaseRegistrarImplementation.sol#L171
The vulnerable line of code is:
require(
expiries[id] + duration + GRACE_PERIOD > duration + GRACE_PERIOD
); // Prevent future overflow
In this code snippet, the duration variable is user-supplied, making it possible to provide a value that would cause an overflow on both sides of the '>' expression, ultimately rendering the condition true. Specifically, when the duration is set to 2^256 - GRACE_PERIOD, the subsequent line expiries[id] += duration; also experiences an overflow, as expiries[id] is greater than GRACE_PERIOD. This results in the reduction of expiries[id] by GRACE_PERIOD. By repeatedly calling the renew function, an attacker could potentially force the expiration of an ENS record.
You can find the PoC included in the attached document. To execute the test, please use the following command:
forge test -vvv --match-contract RegistrarExploit --fork-url <alchemy_url>
Replace <alchemy_url> with your Alchemy API URL. This command will run the Foundry test file and demonstrate the potential vulnerability.
Impact
If successfully exploited, this vulnerability would enable attackers to force the expiration of any ENS record, ultimately allowing them to claim the affected domains for themselves.
Currently, it would require a malicious DAO to exploit it. Nevertheless, any vulnerability present in the controllers could potentially render this issue exploitable in the future.
An additional concern is the possibility of renewal discounts. Should ENS decide to implement a system that offers unlimited .eth domains for a fixed fee in the future, the vulnerability could become exploitable by any user due to the reduced attack cost.
Patches
A mitigation is being developed.
Workarounds
As long as registration cost remains linear or superlinear based on registration duration, or limited to a reasonable maximum (eg, 1 million years), this vulnerability could only be exploited by a malicious DAO. The interim workaround is thus to take no action.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @ensdomains/ens-contracts | all versions | 0.0.22npm install @ensdomains/ens-contracts@0.0.22 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update @ensdomains/ens-contracts to 0.0.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrxv-q8m4-wch3 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 GHSA-rrxv-q8m4-wch3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-rrxv-q8m4-wch3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-rrxv-q8m4-wch3 in your dependencies?
O3 Security finds GHSA-rrxv-q8m4-wch3 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.