How severe is CVE-2025-7962?

No CVSS score has been assigned to CVE-2025-7962 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-7962?

CVE-2025-7962 affects the following packages: org.eclipse.angus:smtp (Maven), com.sun.mail:jakarta.mail (Maven), com.sun.mail:jakarta.mail (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-7962?

Update org.eclipse.angus:smtp to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-7962 is resolved across your whole dependency graph.

How do I detect CVE-2025-7962 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.angus:smtp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-7962 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.

How does O3 Security protect against CVE-2025-7962?

O3 pinpoints whether CVE-2025-7962 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

No public exploit code has been indexed for CVE-2025-7962 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 type of vulnerability is CVE-2025-7962?

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

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

CVE-2025-7962 was published on July 21, 2025 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-7962

CVE-2025-7962 is a CWE-147 vulnerability in org.eclipse.angus:smtp. O3 Security confirms whether CVE-2025-7962 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Jakarta Mail vulnerable to SMTP Injection

Also known asGHSA-9342-92gg-6v29

Published

Jul 21, 2025

Updated

Jul 15, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Real-World Exposure

3 pkgs affected

☕org.eclipse.angus:smtp☕com.sun.mail:jakarta.mail☕com.sun.mail:jakarta.mail

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

Description

In Jakarta Mail versions prior to 2.0.2 it is possible to perform an SMTP Injection by utilizing the \r and \n UTF-8 characters to separate different messages.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.angus:smtp`	all versions	2.0.4
☕Maven	`com.sun.mail:jakarta.mail`	all versions	1.6.8
☕Maven	`com.sun.mail:jakarta.mail`	≥ 2.0.0&&< 2.0.2	2.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.angus:smtp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.eclipse.angus:smtp to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-7962 is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether CVE-2025-7962 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-7962. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Jakarta Mail versions prior to 2.0.2 it is possible to perform an SMTP Injection by utilizing the \r and \n UTF-8 characters to separate different messages.

O3 Security · Impact-Aware SCA

Is CVE-2025-7962 in your dependencies?

O3 detects CVE-2025-7962 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works