Cyber Resilience

CVE-2025-7962

Eclipse Jakarta Mail ≤ 1.6.8

Published
21 July 2025
Modified
23 June 2026
CVSS Score v4 6.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0077 52th percentile
Risk Priority 29 floored blend · peak EPSS

Summary

CVE-2025-7962 is a medium-severity Improper Neutralization of Input Terminators (CWE-147) vulnerability in Eclipse Jakarta Mail. Its CVSS base score is 6.0 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-147

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-8384Same vendor: Eclipse
CVE-2024-6763Same vendor: Eclipse
CVE-2024-9408Same vendor: Eclipse
CVE-2026-2587Same vendor: Eclipse
CVE-2023-24815Same vendor: Eclipse
CVE-2026-12609Same vendor: Eclipse
CVE-2026-12605Same vendor: Eclipse
CVE-2026-1002Same vendor: Eclipse
CVE-2026-24457Same vendor: Eclipse
CVE-2026-2332Same vendor: Eclipse

Affected Assets

eclipse
jakarta mail
≤ 1.6.8 · 2.0.0 — 2.0.2
eclipse
angus mail
≤ 2.0.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation enforces neutralization of terminator characters before data reaches downstream components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input neutralization to prevent terminator-related flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect terminator issues but does not itself implement the neutralization control.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and sanitization that directly prevents improper neutralization of terminators.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for handling of special input elements to avoid injection or termination attacks.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage robust input handling but do not prescribe the specific neutralization technique.

A.8.28 Secure coding partial match
prevents

Secure coding standards require explicit neutralization of input terminators, directly eliminating this weakness.

References