# ALEA-2021:4200: new module: nodejs:16

> This is an enhancement update adding Node.js 16 as a Technology Preview, not a security vulnerability fix.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 9 Nov 2021

## What is ALEA-2021:4200?

ALEA-2021:4200 is a vulnerability in nodejs-packaging, published on 9 Nov 2021. 

### Official description

This enhancement update adds the nodejs:16 module to AlmaLinuxas a Technology Preview. A future update will provide a Long Term Support (LTS) version of Node.js 16, which will be fully supported. (BZ#1953991)

For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.

For information on AlmaLinux scope of support for Technology Preview features, see Technology Preview Features Support Scope.

## Which versions are affected by ALEA-2021:4200?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nodejs-packaging` | AlmaLinux:8 | All versions | 25-1.module_el8.5.0+246+05401605 |
| `nodejs-packaging` | AlmaLinux:8 | All versions | 25-1.module_el8.5.0+2605+45d748af |

## How do I fix ALEA-2021:4200?

Upgrade to a fixed version.

## Is ALEA-2021:4200 being exploited?

There is no known exploitation of ALEA-2021:4200 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALEA-2021:4200 and fix it if it is affected.

What it is: ALEA-2021:4200 is a vulnerability in nodejs-packaging, published on 9 Nov 2021. 
Exploitation: There is no known exploitation of ALEA-2021:4200 in the wild and no public exploit code.

Affected product: nodejs-packaging. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/ALEA-2021-4200/ (Markdown: https://insights.sbomify.com/ALEA-2021-4200/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALEA-2021:4200

---
From sbomify Insights: https://insights.sbomify.com/ALEA-2021-4200/
Summaries are generated and may contain mistakes; the official description above is the record.