# CVE-2025-57319: Other in n/a

> Prototype pollution in fast-redact allows attackers to inject properties into Object.prototype, potentially causing denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** CLSA-2026-1774570934, MINI-2rr6-m95v-2v8r, MINI-3m52-56wg-rj55, MINI-62pp-rq24-x5vg, MINI-cxf6-cwvw-345g, MINI-grg6-9qcx-vxg5, MINI-h4fw-hcx4-g53j, MINI-p3gx-8wr6-33v2, MINI-p727-2rcp-m2xh, MINI-x277-fm3c-wv7p

## What is CVE-2025-57319?

CVE-2025-57319 is a high-severity vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

fast-redact is a package that provides do very fast object redaction. A Prototype Pollution vulnerability in the nestedRestore function of fast-redact version 3.5.0 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence. NOTE: the Supplier disputes this because the reporter only demonstrated access to properties by an internal utility function, and there is no means for achieving prototype pollution via the public API.

## Which versions are affected by CVE-2025-57319?


## How do I fix CVE-2025-57319?

Upgrade to a fixed version.

## Is CVE-2025-57319 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57319 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57319 and fix it if it is affected.

What it is: CVE-2025-57319 is a high-severity vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57319 exists.

Affected product: n/a. 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/CVE-2025-57319/ (Markdown: https://insights.sbomify.com/CVE-2025-57319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57319
- OSV: https://osv.dev/vulnerability/CVE-2025-57319

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