@alizeait/unflatto Prototype Pollution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:P · score source

EPSS

• CVE-2024-38988: 0.87% estimated exploitation activity in the next 30 days; percentile 58.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact alizeait unflatto <= 1.0.2 was discovered to contain a prototype pollution via the method exports.unflatto at /dist/index.js. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties. Patches The problem has been patched in 1.0.3 References https://github.com/advisories/GHSA-799q-f2px-wx8c

Published by the source

1 Apr 2025, 14:54 UTC

Last modified by the source

1 Apr 2025, 15:27 UTC

Source last checked

26 Oct 2026, 12:36 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-q8jq-4rm5-4hm5

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-q8jq-4rm5-4hm5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-38988

Advisory: @alizeait/unflatto Prototype Pollution
IDs: CVE-2024-38988, GHSA-q8jq-4rm5-4hm5
Record: https://patchnext.com/advisories/cve-2024-38988 (revision 3, source checked 26 Oct 2026, 12:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @alizeait/unflatto 1.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @alizeait/unflatto: affected < 1.0.3; fixed in 1.0.3

## Suggested inspection (read-only)
- `npm ls @alizeait/unflatto --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @alizeait/unflatto.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-q8jq-4rm5-4hm5 (OSV record GHSA-q8jq-4rm5-4hm5 lists affected ranges: npm @alizeait/unflatto >=0 <1.0.3 (fixed))
- Verified: https://github.com/advisories/GHSA-q8jq-4rm5-4hm5 (GitHub-reviewed advisory GHSA-q8jq-4rm5-4hm5 lists affected ranges: npm @alizeait/unflatto >=0 <1.0.3)

Commands are suggestions: review each one before running it.