How severe is CVE-2025-27611?

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

Which packages are affected by CVE-2025-27611?

CVE-2025-27611 affects the following packages: base-x (npm), base-x (npm), base-x (npm). Ecosystems affected: npm.

How do I fix CVE-2025-27611?

Update base-x to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27611 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2025-27611 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-27611?

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

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

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

CVE-2025-27611 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th 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-27611?

CVE-2025-27611 is classified as CWE-1007 (CWE-1007). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2025-27611 was published on April 30, 2025 and was last updated on August 12, 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-27611 — base-x

Fix: cryptocoinjs/base-x#86

CVE-2025-27611 is a CWE-1007 vulnerability in base-x. A fix is available for base-x — see the affected versions and patch details below.

base-x homograph attack allows Unicode lookalike characters to bypass validation.

Also known asGHSA-xq7p-g2vc-g82p

Published

Apr 30, 2025

Updated

Aug 12, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 22, 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-27611.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% 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

3 pkgs 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.

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

base-xnpm

8.9Mdownloads / week

Description

base-x is a base encoder and decoder of any given alphabet using bitcoin style leading zero compression. Versions 4.0.0, 5.0.0, and all prior to 3.0.11, are vulnerable to attackers potentially deceiving users into sending funds to an unintended address. This issue has been patched in versions 3.0.11, 4.0.1, and 5.0.1.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`base-x`	≥ 5.0.0&&< 5.0.1	5.0.1`npm install base-x@5.0.1`
📦npm	`base-x`	≥ 4.0.0&&< 4.0.1	4.0.1`npm install base-x@4.0.1`
📦npm	`base-x`	all versions	3.0.11`npm install base-x@3.0.11`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for base-x, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update base-x to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27611 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-27611 can be triaged on real exposure rather than presence alone.

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

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability in base-x is Important because it affects the encoding and decoding of addresses in blockchain transactions. The flaw arises from mishandling of leading zero compression, enabling attackers to craft malicious encodings that deceive systems or users into misdirecting funds. As blockchain transactions…

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform 8.0.8	`org.jboss.hal-hal-parent`	RHSA-2025:10459
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8	`eap8-activemq-artemis-0:2.33.0-3.redhat_00017.1.el8eap`	RHSA-2025:10452
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9	`eap8-activemq-artemis-0:2.33.0-3.redhat_00017.1.el9eap`	RHSA-2025:10453

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-27611 in your dependencies?

O3 Security finds CVE-2025-27611 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