Skip to main content
VulnerabilityPublished

CVE-2025-14763: AWS S3 Encryption Client for Java · Weak Cryptography

Affects AWS S3 Encryption Client for JavaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.0.0 when convenient.

Data as of 16 Nov 2026, 20:24 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade com.amazonaws/amazon-s3-encryption-client to 4.0.0.

Affected software

ProductAffectedFixed in
Mavencom.amazonaws/amazon-s3-encryption-clientpkg:maven/com.amazonaws/amazon-s3-encryption-clientOther threatsAffected
  • <4.0.0
Fixed in
  • 4.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the Amazon S3 Encryption Client for Java to version 4.0.0 or later. This version includes the necessary cryptographic key commitment to mitigate the vulnerability. No other mitigations are specified or required.

Description

CVE-2025-14763 is a medium severity vulnerability in the Amazon S3 Encryption Client for Java prior to version 4.0.0. It involves the use of a broken or risky cryptographic algorithm due to missing cryptographic key commitment. This flaw allows a user with write access to an S3 bucket to introduce a new encrypted data key (EDK) that decrypts to different plaintext when the encrypted data key is stored in an instruction file rather than in S3's metadata. The issue is fixed in version 4.0.0 and later.

References

Community reviews

Loading reviews…