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

Babel: Arbitrary File Read via sourceMappingURL Comment in @babel/core

babel · babel

Official source article: GitHub GHSA-4X5R-PXFX-6JF8 ↗. Check the applicable product and release in the original source.

3.2LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.15% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs babel babel and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  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: No default targetRemediation target: Normal maintenance

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.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

4 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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-babel7Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-babel7Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-babel7Vendor fix publishedDebian records a fixed source-package version for this release.8.0.4+ds1+~cs177.303.116-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-babel7Vendor fix publishedDebian records a fixed source-package version for this release.8.0.4+ds1+~cs177.303.116-2Debian Security Tracker ↗Source updated 6 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
npm@babel/core>= 8.0.0-alpha.0, < 8.0.0-rc.58.0.0-rc.6GitHub advisory ↗upstream repository advisory · 15 Jul 2026
npm@babel/core<= 7.29.07.29.6GitHub advisory ↗upstream repository advisory · 15 Jul 2026
npm@babel/coreSEMVER: introduced 8.0.0-alpha.0; fixed 8.0.0-rc.68.0.0-rc.6OSV record ↗aggregator derived · 10 Sep 2026
npm@babel/coreSEMVER: introduced 0; fixed 7.29.67.29.6OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-49356 · CSAF 2.0 · revision 6 · interimSUSE Product Security TeamCVE-2026-49356
118 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • pgadmin4 as component of SUSE Linux Enterprise Desktop 15 SP7
  • pgadmin4-doc as component of SUSE Linux Enterprise Desktop 15 SP7
  • pgadmin4-web as component of SUSE Linux Enterprise Desktop 15 SP7
  • system-user-pgadmin as component of SUSE Linux Enterprise Desktop 15 SP7
  • pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • pgadmin4-web as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • pgadmin4-web as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
Babel is a compiler for writing next generation JavaScript. Prior to 8.0.0-rc.6 and 7.29.6, @babel/core affected by an arbitrary file read via a sourceMappingURL comment. Using @babel/core to compile maliciously crafted code can allow an attacker to read any source map from the system that is running Babel, if the attacker controls the input source code, can read the output source code, and knows the path of the source map file that they want to read. This vulnerability is fixed in 8.0.0-rc.6 and 7.29.6.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-38302

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 actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Babel is a compiler for writing next generation JavaScript. Prior to 8.0.0-rc.6 and 7.29.6, @babel/core affected by an arbitrary file read via a sourceMappingURL comment. Using @babel/core to compile maliciously crafted code can allow an attacker to read any source map from the system that is running Babel, if the attacker controls the input source code, can read the output source code, and knows the path of the source map file that they want to read. This vulnerability is fixed in 8.0.0-rc.6 and 7.29.6.

What

Babel is a compiler for writing next generation JavaScript. Prior to 8.0.0-rc.6 and 7.29.6, @babel/core affected by an arbitrary file read via a sourceMappingURL comment. Using @babel/core to compile maliciously crafted code can allow an attacker to read any source map from the system that is running Babel, if the attacker controls the input source code, can read the output source code, and knows the path of the source map file that they want to read. This vulnerability is fixed in 8.0.0-rc.6 and 7.29.6.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through local access 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

Babel is a compiler for writing next generation JavaScript. Prior to 8.0.0-rc.6 and 7.29.6, @babel/core affected by an arbitrary file read via a sourceMappingURL comment. Using @babel/core to compile maliciously crafted code can allow an attacker to read any source map from the system that is running Babel, if the attacker controls the input source code, can read the output source code, and knows the path of the source map file that they want to read. This vulnerability is fixed in 8.0.0-rc.6 and 7.29.6.

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through local access 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.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-22 ↗

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CLowConfidentiality impact: A successful attack can cause a limited loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-22
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20260624Security Bulletin 24 June 2026

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

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

ecord?id=CVE-2026-45991 Référence CVE CVE-2026-46120 https://www.cve.org/CVERecord?id=CVE-2026-46120 Référence CVE CVE-2026-4800 https://www.cve.org/CVERecord?id=CVE-2026-4800 Référence CVE CVE-2026-48586 https://www.cve.org/CVERecord?id=CVE-2026-48586 Référence CVE CVE-2026-4867 https://www.cve.org/CVERecord?id=CVE-2026-4867 Référence CVE CVE-2026-48801 https://www.cve.org/CVERecord?id=CVE-2026-48801 Référence CVE CVE-2026-48913 https://www.cve.org/CVERecord?id=CVE-2026-48913 Référence CVE CVE-2026-48988 https://www.cve.org/CVERecord?id=CVE-2026-48988 Référence CVE CVE-2026-49268 https://www.cve.org/CVERecord?id=CVE-2026-49268 Référence CVE CVE-2026-49356 https://www.cve.org/CVERecord?id=CVE-2026-49356 Référence CVE CVE-2026-49458 https://www.cve.org/CVERecord?id=CVE-2026-49458 Référence CVE CVE-2026-49459 https://www.cve.org/CVERecord?id=CVE-2026-49459 Référence CVE CVE-2026-49844 https://www.cve.org/CVERecord?id=CVE-2026-49844 Référence CVE CVE-2026-49975 https://www.cve.org/CVERecord?id=CVE-2026-49975 Référence CVE CVE-2026-49978 https://www.cve.org/CVERecord?id=CVE-2026-49978 Référence CVE CVE-2026-5038 https://www.cve.org/CVERecord?id=CVE-2026-5038 Référence CVE CVE-2026-5078 https://www.cve.org/CVERecord?id=CVE-2026-5078 Référence CVE CVE-2026-5079 https://www.cve.org/CVERecord?id=CVE-2

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

ord?id=CVE-2026-47010 Référence CVE CVE-2026-47021 https://www.cve.org/CVERecord?id=CVE-2026-47021 Référence CVE CVE-2026-47027 https://www.cve.org/CVERecord?id=CVE-2026-47027 Référence CVE CVE-2026-47057 https://www.cve.org/CVERecord?id=CVE-2026-47057 Référence CVE CVE-2026-47058 https://www.cve.org/CVERecord?id=CVE-2026-47058 Référence CVE CVE-2026-47059 https://www.cve.org/CVERecord?id=CVE-2026-47059 Référence CVE CVE-2026-47063 https://www.cve.org/CVERecord?id=CVE-2026-47063 Référence CVE CVE-2026-4873 https://www.cve.org/CVERecord?id=CVE-2026-4873 Référence CVE CVE-2026-48779 https://www.cve.org/CVERecord?id=CVE-2026-48779 Référence CVE CVE-2026-49356 https://www.cve.org/CVERecord?id=CVE-2026-49356 Référence CVE CVE-2026-49875 https://www.cve.org/CVERecord?id=CVE-2026-49875 Référence CVE CVE-2026-53550 https://www.cve.org/CVERecord?id=CVE-2026-53550 Référence CVE CVE-2026-53666 https://www.cve.org/CVERecord?id=CVE-2026-53666 Référence CVE CVE-2026-53668 https://www.cve.org/CVERecord?id=CVE-2026-53668 Référence CVE CVE-2026-53669 https://www.cve.org/CVERecord?id=CVE-2026-53669 Référence CVE CVE-2026-55602 https://www.cve.org/CVERecord?id=CVE-2026-55602 Référence CVE CVE-2026-55603 https://www.cve.org/CVERecord?id=CVE-2026-55603 Référence CVE CVE-2026-58059 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-021290Babelにおける複数の脆弱性

Babelは次世代のJavaScriptを書くためのコンパイラです。8.0.0-rc.6および7.29.6以前のバージョンでは、@babel/coreがsourceMappingURLコメントを介した任意のファイル読み取りの影響を受けます。@babel/coreを使用して悪意のある細工がされたコードをコンパイルすると、攻撃者が入力ソースコードを制御し、出力ソースコードを読み取ることができます。また、読み取りたいソースマップファイルのパスを知っている場合には、Babelを実行しているシステム上の任意のソースマップを読み取ることが可能になります。この脆弱性は8.0.0-rc.6および7.29.6で修正されました。

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 availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 22 Jun 2026 · Last source change 22 Jun 2026, 17:23 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

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-38302
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

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
CVE published
Mitigation reference recorded
ENISA EUVD · EUVD-2026-38302↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference · GitHub GHSA-4X5R-PXFX-6JF8↗Official CVE record (CNA and ADP data)↗NVD record↗
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-49356 · cve.blacktree.nl