CVE-2026-44728
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBabel is a compiler for writing next generation JavaScript. From 7.12.0 to before 7.29.4 and 8.0.0-alpha.13, using Babel to compile code that was specifically crafted by an attacker can cause Babel to generate output code that executes arbitrary code. This vulnerability is fixed in 7.29.4 and 8.0.0-alpha.13.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a code generation vulnerability in Babel where specially crafted attacker-controlled input code causes Babel to generate output that executes arbitrary code. The vulnerability stems from insufficient validation during the compilation process, allowing malicious input to produce unsafe output code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.12.0, < 7.29.4= 8.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Babel versionRun `npm list @babel/core` or `npm list @babel/compiler` in your project directory, or inspect the version field in your package.json fileAffected if The version shown is >= 7.12.0 and < 7.29.4, or equals 8.0.0-alpha.12
-
Identify Babel packages in useRun `npm list --depth=0` to list all top-level Babel-related packages installed in your projectAffected if Any Babel package listed matches the affected version range from step 1
-
Determine if Babel processes untrusted inputReview your application code to see whether Babel's transform or compile functions are called on JavaScript that comes from untrusted sources such as user upload, API input, or external APIsAffected if Your application passes untrusted JavaScript to Babel for compilation or transformation
You are affected if Babel version is 7.12.0-7.29.3 or 8.0.0-alpha.12 AND your application uses Babel to compile or transform untrusted JavaScript code.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.29.4
Upgrade Babel to version 7.29.4 or later (or 8.0.0-alpha.13+) to obtain the security fix, then verify that compiled output remains functionally correct.
7.29.4 (for 7.x users) or 8.0.0-alpha.13 or later (for 8.x users)
- Check your current Babel version by running `npm list @babel/core` or looking in your package.json
- For Babel 7.x users: Upgrade to version 7.29.4 or later by running `npm install @babel/core@^7.29.4`
- For Babel 8.x users: Upgrade to version 8.0.0-alpha.13 or later (note: 8.0.0 stable is also affected)
- After upgrading, rebuild/recompile your project to ensure the new Babel version is used
- Verify the fix by compiling the previously vulnerable code pattern and confirming it no longer produces unsafe output
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data