CVE-2025-3877 This CVE was marked as fixed, but due to other code landing - was not actually fixed.
Not scored
Published
Updated
Check this codebase for CVE-2025-3877 and fix it if it is affected.
What it is: CVE-2025-3877 is a vulnerability, published on 14 May 2025.
Exploitation: There is no known exploitation of CVE-2025-3877 in the wild and no public exploit code.
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-3877/ (Markdown: https://insights.sbomify.com/CVE-2025-3877/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2025-3877?
CVE-2025-3877 is a vulnerability, published on 14 May 2025.
Official description
This CVE was marked as fixed, but due to other code landing - was not actually fixed. It was subsequently fixed in CVE-2025-5986.
Which versions are affected by CVE-2025-3877?
How do I fix CVE-2025-3877?
Upgrade to a fixed version.
Is CVE-2025-3877 being exploited?
There is no known exploitation of CVE-2025-3877 in the wild and no public exploit code.
Sources
Also known as GHSA-69m9-2g5j-9m4h.