CVE-2025-7962
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Jakarta Mail versions prior to 2.0.2, the mail component fails to properly sanitize input containing carriage return (\r) and newline (\n) UTF-8 characters. This allows an attacker to inject additional SMTP commands and separate a single email message into multiple messages, potentially enabling spam distribution or email-based attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.6.8>= 2.0.0, < 2.0.2< 2.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Jakarta Mail or Angus Mail in useLocate the mail JAR file in your application (e.g., jakarta.mail.jar, angus-mail.jar) or check Maven/Gradle dependencies for jakarta.mail:mail or org.eclipse.angus:angus-mailAffected if The JAR or dependency exists in your application
-
Check installed Jakarta Mail versionInspect the JAR manifest or check the dependency version in your build file (pom.xml, build.gradle) - look for version numbers like 1.6.x, 1.5.x, 2.0.x, or 2.0.0-2.0.1Affected if Version is less than 1.6.8, OR version is 2.0.0, 2.0.1, or any 2.0.x version prior to 2.0.2
-
Check installed Angus Mail versionIf using Angus Mail instead, inspect the JAR version or dependency declaration - typically named angus-mailAffected if Version is less than 2.0.4
-
Confirm SMTP transport is usedReview code that uses jakarta.mail. Look for Session.getInstance() with SMTP transport (Transport.send() or Session.getTransport("smtp")). The vulnerability affects SMTP command injection.Affected if Your application sends email via SMTP protocol (the vast majority of Jakarta Mail use cases)
-
Inspect email input handlingAudit code paths where user-provided data (subject, body, recipients, headers) flows into MimeMessage.setSubject(), setFrom(), setText(), or related methods without sanitizationAffected if User-controlled input reaches email-sending methods without CRLF character filtering
You are affected if Jakarta Mail version is below 1.6.8, between 2.0.0-2.0.1 inclusive, or Angus Mail version is below 2.0.4, and your application sends email via SMTP with unsanitized user input in email fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.6.82.0.22.0.4
Upgrade Jakarta Mail to version 2.0.2 or later to incorporate the fix that properly sanitizes input and prevents CRLF injection in SMTP communications.
Jakarta Mail 1.6.8 or 2.0.2; Angus Mail 2.0.4
- Identify the current Jakarta Mail or Angus Mail version in use by checking project dependencies (e.g., pom.xml, build.gradle, or manifest files)
- For Jakarta Mail 1.x (versions < 1.6.8): Upgrade Jakarta Mail dependency to version 1.6.8 or later
- For Jakarta Mail 2.x (versions >= 2.0.0 and < 2.0.2): Upgrade Jakarta Mail dependency to version 2.0.2 or later
- For Angus Mail (versions < 2.0.4): Upgrade Angus Mail dependency to version 2.0.4 or later
- Rebuild the application and run tests to verify the upgrade does not introduce regressions
- Verify that SMTP injection protection is working by testing with inputs containing \r and \n characters
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7962 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data