Cache Poisoning Vulnerability

Exploitation

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

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2024-29042: 0.65% estimated exploitation activity in the next 30 days; percentile 51.19 (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.

Summary An attacker controlling the second variable of the translate function is able to perform a cache poisoning attack. They can change the outcome of translation requests made by subsequent users. Details The opt.id parameter allows the overwriting of the cache key. If an attacker sets the id variable to the cache key that would be generated by another user, they can choose the response that user gets served. PoC Take the following simple server allowing users to supply text and the language to translate to. We can send the following request to poison the cache: Now, any user that attempts to translate "I love you" to Dutch, will get "I hate you" in Dutch as the response. Impact An attacker can control the results other users may get

Published by the source

22 Mar 2024, 16:57 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 12:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-882j-4vj5-7vmj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-882j-4vj5-7vmj

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

# Patch Next advisory brief: CVE-2024-29042

Advisory: Cache Poisoning Vulnerability
IDs: CVE-2024-29042, GHSA-882j-4vj5-7vmj
Record: https://patchnext.com/advisories/cve-2024-29042 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: translate 3.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm translate: affected < 3.0.0; fixed in 3.0.0

## Suggested inspection (read-only)
- `npm ls translate --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 translate.
- 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-882j-4vj5-7vmj (OSV record GHSA-882j-4vj5-7vmj lists affected ranges: npm translate >=0 <3.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-882j-4vj5-7vmj (GitHub-reviewed advisory GHSA-882j-4vj5-7vmj lists affected ranges: npm translate >=0 <3.0.0)

Commands are suggestions: review each one before running it.