CVE-2025-27498

What it is

aes-gcm is a pure Rust implementation of the AES-GCM. In decrypt_in_place_detached, the decrypted ciphertext (which is the correct ciphertext) is exposed even if the tag is incorrect. This is because in decrypt_inplace in asconcore.rs, tag verification causes an error to be returned with the plaintext contents still in buffer. The vulnerability is fixed in 0.4.3.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data tampering.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-03-03 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 09:03 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 5.7 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-03-03 17:15 UTC

Last modified

2026-06-17 09:03 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-347

Record status

Deferred

Attack profile CVSS 4.0 · 5.7

Attack vector

Local

Complexity

High

Attack requirements

None

Privileges needed

None

User interaction

Active

Confidentiality

Low

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-27498.md and follow it. Check whether this project is affected by CVE-2025-27498. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge