BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-2739High confidence

This affects versions of the package bn.js before 5.2.3

Unknown · bn.js

6.9MediumCVSS 4.0
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 20 Feb 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.60% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown bn.js and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenode-bn.jsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenode-bn.jsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenode-bn.jsVendor fix publishedDebian records a fixed source-package version for this release.5.2.3+~5.2.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenode-bn.jsVendor fix publishedDebian records a fixed source-package version for this release.5.2.3+~5.2.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-bn.jsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmbn.js< 4.12.34.12.3GitHub advisory ↗github reviewed aggregator · 24 Feb 2026
npmbn.js>= 5.0.0, < 5.2.35.2.3GitHub advisory ↗github reviewed aggregator · 24 Feb 2026
npmbn.jsSEMVER: introduced 0; fixed 4.12.34.12.3OSV record ↗aggregator derived · 10 Sep 2026
npmbn.jsSEMVER: introduced 5.0.0; fixed 5.2.35.2.3OSV record ↗aggregator derived · 10 Sep 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-8025

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

This affects versions of the package bn.js before 5.2.3. Calling maskn(0) on any BN instance corrupts the internal state, causing toString(), divmod(), and other methods to enter an infinite loop, hanging the process indefinitely.

What

This affects versions of the package bn.js before 5.2.3. Calling maskn(0) on any BN instance corrupts the internal state, causing toString(), divmod(), and other methods to enter an infinite loop, hanging the process indefinitely.

Why

A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

This affects versions of the package bn.js before 5.2.3. Calling maskn(0) on any BN instance corrupts the internal state, causing toString(), divmod(), and other methods to enter an infinite loop, hanging the process indefinitely.

Why

A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Loop with Unreachable Exit Condition ('Infinite Loop') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-835 ↗

CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop'). The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-835Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2933Splunk SOAR: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk SOAR ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um beliebigen Programmcode auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260225Security Bulletin 25 Feb 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 25 Feb 2026, published on 25 February 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-23216 Référence CVE CVE-2026-2359 https://www.cve.org/CVERecord?id=CVE-2026-2359 Référence CVE CVE-2026-23865 https://www.cve.org/CVERecord?id=CVE-2026-23865 Référence CVE CVE-2026-2482 https://www.cve.org/CVERecord?id=CVE-2026-2482 Référence CVE CVE-2026-25243 https://www.cve.org/CVERecord?id=CVE-2026-25243 Référence CVE CVE-2026-25749 https://www.cve.org/CVERecord?id=CVE-2026-25749 Référence CVE CVE-2026-26007 https://www.cve.org/CVERecord?id=CVE-2026-26007 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27205 https://www.cve.org/CVERecord?id=CVE-2026-27205 Référence CVE CVE-2026-2739 https://www.cve.org/CVERecord?id=CVE-2026-2739 Référence CVE CVE-2026-27601 https://www.cve.org/CVERecord?id=CVE-2026-27601 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31692 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1056Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-25679 Référence CVE CVE-2026-25755 https://www.cve.org/CVERecord?id=CVE-2026-25755 Référence CVE CVE-2026-25940 https://www.cve.org/CVERecord?id=CVE-2026-25940 Référence CVE CVE-2026-26007 https://www.cve.org/CVERecord?id=CVE-2026-26007 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27140 https://www.cve.org/CVERecord?id=CVE-2026-27140 Référence CVE CVE-2026-27143 https://www.cve.org/CVERecord?id=CVE-2026-27143 Référence CVE CVE-2026-27144 https://www.cve.org/CVERecord?id=CVE-2026-27144 Référence CVE CVE-2026-27199 https://www.cve.org/CVERecord?id=CVE-2026-27199 Référence CVE CVE-2026-2739 https://www.cve.org/CVERecord?id=CVE-2026-2739 Référence CVE CVE-2026-27651 https://www.cve.org/CVERecord?id=CVE-2026-27651 Référence CVE CVE-2026-27654 https://www.cve.org/CVERecord?id=CVE-2026-27654 Référence CVE CVE-2026-27784 https://www.cve.org/CVERecord?id=CVE-2026-27784 Référence CVE CVE-2026-27959 https://www.cve.org/CVERecord?id=CVE-2026-27959 Référence CVE CVE-2026-28277 https://www.cve.org/CVERecord?id=CVE-2026-28277 Référence CVE CVE-2026-28388 https://www.cve.org/CVERecord?id=CVE-2026-28388 Référence CVE CVE-2026-28389 https://www.cve.org/CVERecord?id=CVE-2026-28389 Référence CVE CVE-2026-28390 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0901Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-25639 Référence CVE CVE-2026-25645 https://www.cve.org/CVERecord?id=CVE-2026-25645 Référence CVE CVE-2026-25680 https://www.cve.org/CVERecord?id=CVE-2026-25680 Référence CVE CVE-2026-25681 https://www.cve.org/CVERecord?id=CVE-2026-25681 Référence CVE CVE-2026-26960 https://www.cve.org/CVERecord?id=CVE-2026-26960 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27136 https://www.cve.org/CVERecord?id=CVE-2026-27136 Référence CVE CVE-2026-27199 https://www.cve.org/CVERecord?id=CVE-2026-27199 Référence CVE CVE-2026-27205 https://www.cve.org/CVERecord?id=CVE-2026-27205 Référence CVE CVE-2026-2739 https://www.cve.org/CVERecord?id=CVE-2026-2739 Référence CVE CVE-2026-27448 https://www.cve.org/CVERecord?id=CVE-2026-27448 Référence CVE CVE-2026-27459 https://www.cve.org/CVERecord?id=CVE-2026-27459 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-27980 https://www.cve.org/CVERecord?id=CVE-2026-27980 Référence CVE CVE-2026-28684 https://www.cve.org/CVERecord?id=CVE-2026-28684 Référence CVE CVE-2026-29057 https://www.cve.org/CVERecord?id=CVE-2026-29057 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0667Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-25547 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-2581 https://www.cve.org/CVERecord?id=CVE-2026-2581 Référence CVE CVE-2026-25896 https://www.cve.org/CVERecord?id=CVE-2026-25896 Référence CVE CVE-2026-26278 https://www.cve.org/CVERecord?id=CVE-2026-26278 Référence CVE CVE-2026-26960 https://www.cve.org/CVERecord?id=CVE-2026-26960 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27135 https://www.cve.org/CVERecord?id=CVE-2026-27135 Référence CVE CVE-2026-27199 https://www.cve.org/CVERecord?id=CVE-2026-27199 Référence CVE CVE-2026-2739 https://www.cve.org/CVERecord?id=CVE-2026-2739 Référence CVE CVE-2026-27448 https://www.cve.org/CVERecord?id=CVE-2026-27448 Référence CVE CVE-2026-27459 https://www.cve.org/CVERecord?id=CVE-2026-27459 Référence CVE CVE-2026-27699 https://www.cve.org/CVERecord?id=CVE-2026-27699 Référence CVE CVE-2026-27837 https://www.cve.org/CVERecord?id=CVE-2026-27837 Référence CVE CVE-2026-27903 https://www.cve.org/CVERecord?id=CVE-2026-27903 Référence CVE CVE-2026-27904 https://www.cve.org/CVERecord?id=CVE-2026-27904 Référence CVE CVE-2026-27942 https://www.cve.org/CVERecord?id=CVE-2026-27942 Référence CVE CVE-2026-27980 https://www.cve.org/CVERecord?id=C

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
bn.js: < 5.2.3
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 20 Feb 2026 · Last source change 20 Feb 2026, 15:03 UTC · CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-8025
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD not scheduled

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-2739 · cve.blacktree.nl