Jakarta Mail vulnerable to SMTP Injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.0 · CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N · score source

EPSS

• CVE-2025-7962: 0.89% estimated exploitation activity in the next 30 days; percentile 59.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In Jakarta Mail 2.2 it is possible to preform a SMTP Injection by utilizing the \r and \n UTF-8 characters to separate different messages.

Published by the source

21 Jul 2025, 18:32 UTC

Last modified by the source

16 Apr 2026, 18:47 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9342-92gg-6v29

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-7962

Advisory: Jakarta Mail vulnerable to SMTP Injection
IDs: CVE-2025-7962, GHSA-9342-92gg-6v29
Record: https://patchnext.com/advisories/cve-2025-7962 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.sun.mail:jakarta.mail 2.0.2, 1.6.8; org.eclipse.angus:smtp 2.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.sun.mail:jakarta.mail: affected < 1.6.8; >= 2.0.0, < 2.0.2; fixed in 2.0.2, 1.6.8
- Maven org.eclipse.angus:smtp: affected < 2.0.4; fixed in 2.0.4

## Suggested inspection (read-only)
- Maven com.sun.mail:jakarta.mail: check the installed version with your package manager.
- Maven org.eclipse.angus:smtp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.sun.mail:jakarta.mail, org.eclipse.angus:smtp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9342-92gg-6v29 (GitHub-reviewed advisory GHSA-9342-92gg-6v29 lists affected ranges: Maven org.eclipse.angus:smtp >=0 =0 =2.0.0 <2.0.2)

Commands are suggestions: review each one before running it.