# GHSA-8qm3-746x-r74r: devalue `uneval`ed code can create objects with polluted prototypes when `eval`ed

> Attackers can achieve code execution by exploiting prototype pollution in the devalue library when unevaluated data is later evaluated.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2026

## What is GHSA-8qm3-746x-r74r?

GHSA-8qm3-746x-r74r is a code injection vulnerability in devalue, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Under certain circumstances, `uneval`ing untrusted data can produce output code that will create objects with polluted prototypes when later `eval`ed, meaning the output data can be a different shape from the input data.

## Which versions are affected by GHSA-8qm3-746x-r74r?

2 open source packages ship an affected version, including devalue.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `devalue` | npm | All versions | 5.6.3 |
| `devalue` | npm | All versions | 5.6.3 |

## How do I fix GHSA-8qm3-746x-r74r?

Upgrade devalue to 5.6.3 or later.

## Is GHSA-8qm3-746x-r74r being exploited?

There is no known exploitation of GHSA-8qm3-746x-r74r in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8qm3-746x-r74r and fix it if it is affected.

What it is: GHSA-8qm3-746x-r74r is a code injection vulnerability in devalue, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-8qm3-746x-r74r in the wild and no public exploit code.

Affected packages and fixed versions:
- devalue (npm): affected all versions; fixed in 5.6.3
- devalue (npm): affected all versions; fixed in 5.6.3

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/GHSA-8qm3-746x-r74r/ (Markdown: https://insights.sbomify.com/GHSA-8qm3-746x-r74r/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8qm3-746x-r74r

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8qm3-746x-r74r/
Summaries are generated and may contain mistakes; the official description above is the record.