How severe is CVE-2025-47737?

CVE-2025-47737 has a CVSS score of 2.9/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-47737?

CVE-2025-47737 affects the following packages: trailer (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2025-47737?

The records we use list no patched version of trailer for CVE-2025-47737. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2025-47737 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trailer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-47737 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-47737 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-47737 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-47737?

CVE-2025-47737 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-47737?

CVE-2025-47737 is classified as CWE-762 (CWE-762). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-47737 published, and has it been updated?

CVE-2025-47737 was published on May 9, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

LOW severity

CVE-2025-47737 — trailer

LOW

CVE-2025-47737 is a low-severity (CVSS 2.9) CWE-762 vulnerability in trailer. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

trailer mishandles allocating with a size of zero

Also known asGHSA-6x45-r4pr-5362RUSTSEC-2025-0163

Published

May 9, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-47737.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🦀trailer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

lib.rs in the trailer crate through 0.1.2 for Rust mishandles allocating with a size of zero.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`trailer`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

trailerunhandledexpression

≤ 0.1.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for trailer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of trailer for CVE-2025-47737. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

lib.rs in the trailer crate through 0.1.2 for Rust mishandles allocating with a size of zero.

O3 Security · Impact-Aware SCA

Is CVE-2025-47737 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works