On this page (7 sections)
Ubuntu has published security notice USN-9054-1 about a vulnerability in Babel, the widely used JavaScript compiler. According to the notice, Babel incorrectly evaluated certain code during compilation when used with certain plugins, which could allow arbitrary code execution if someone compiled specially crafted code.
If you run Ubuntu servers, build machines or CI runners that compile JavaScript, or you accept code from outside your team into a build, this notice is worth a few minutes of your time. The public detail is limited, so this article separates what is confirmed from what is not.
What the notice says
The Ubuntu notice describes the problem in one short passage. Babel evaluated certain code during compilation when used with certain plugins. If a user or an automated system were tricked into compiling specially crafted code, an attacker could possibly use the issue to execute arbitrary code.
That is the full technical description available to us. The research for this story contains no CVE identifier, no severity score, no list of affected plugins, and no package versions. Only one independent publisher covers the story so far, so there is no second source to confirm or expand on these details. Check the notice directly for the exact package versions fixed on each Ubuntu release.
Why compile-time code evaluation matters
A compiler like Babel reads source code and rewrites it, for example turning modern JavaScript into a form older browsers understand. Normally that is a pure text transformation: the input is data, and nothing in it runs during the build.
The weakness described here is of a different kind. If the tool evaluates part of the input as code while compiling, the input stops being passive data. Whoever controls that input can influence what runs on the machine doing the build, with the permissions of the account running it. That is why the notice frames the risk as arbitrary code execution rather than a crash or a wrong output.
The notice says a user or automated system must be tricked into compiling crafted code. So the realistic risk depends on where your build input comes from.
Who is realistically exposed
- CI/CD runners and build servers on Ubuntu that run Babel against pull requests or contributions from people you do not fully trust.
- Developer workstations on Ubuntu that compile code from unfamiliar repositories or downloaded projects.
- Services that compile user-supplied JavaScript on the fly, such as online editors, playgrounds or template tools.
- Hosting environments where several customers or projects share one build machine.
If Babel only ever compiles code written and reviewed by your own team, the exposure is lower, though keeping the package updated is still sensible. Build machines often hold deployment keys, tokens and access to production, which raises the stakes of any code execution there.
How to check your exposure
First find out whether Babel is installed through the Ubuntu package manager. This read-only command lists installed packages whose names contain babel; look at the package names and versions in the output and compare them with the notice.
dpkg -l | grep -i babelMany projects install Babel through npm inside the project itself rather than through apt. The Ubuntu notice concerns Ubuntu packages, and the available source does not say whether npm copies are affected. This read-only command, run in a project directory, shows installed Babel packages and their versions.
npm ls | grep -i babelAlso review your build configuration for Babel plugins, and note which of your pipelines process code from outside your team. The notice says the issue arises with certain plugins, but the source does not say which, so treat any plugin-using pipeline as worth checking until you have details.
What to do now
- Read USN-9054-1 and note the fixed package versions for your Ubuntu release.
- Run the dpkg check above on servers, CI runners and workstations to find installed Babel packages.
- Update the affected packages through your normal process (for example, refresh the package index with sudo apt update, install the updated package), then confirm the new version with dpkg -l.
- Check project-level npm installs of Babel and review their upstream release notes, since an Ubuntu package update will not change them.
- Until patched, avoid compiling code from untrusted sources on machines that hold secrets or deploy keys.
- Run builds of outside contributions in isolated, short-lived environments with minimal credentials.
- If you compile untrusted code, review recent build logs for unexpected processes, network connections or changed files.
Detection and monitoring afterwards
Code execution on a build machine often does not show up on the website itself, but its effects can. A compromised build could alter the JavaScript you ship to visitors. Compare deployed bundles against what you expect, watch for new or changed scripts on your pages, and keep build credentials short-lived and tightly scoped.
For the public side of your site, outside-in checks can help you notice unexpected changes, such as altered security headers or new certificates. Webforta Monitor tracks header, certificate and DNS changes, and the free security headers checker gives a quick view of your current headers. These do not detect this Babel issue; they help you spot downstream changes.
If you suspect a build machine was compromised, follow the steps in website hacked: what to do and rotate any tokens or keys the machine could reach.
What we do not know yet
- Which Babel plugins trigger the problem.
- Whether a CVE identifier or CVSS score exists.
- Which package versions are affected and which contain the fix on each Ubuntu release.
- Whether anyone is exploiting it. The available source does not mention exploitation either way.
- Whether Babel installed through npm is affected in the same way.
We will treat these as open until the notice or upstream sources say otherwise. For other recent Ubuntu notices, see USN-9055-1: pecl_http Type Confusion Notice from Ubuntu and USN-9058-1: Action Pack Page Caching Flaw, What to Check, or browse the Webforta security blog.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
