cve.bz

CVE-2026-6986 cesanta mongoose

2.9 lowExploit referenceEPSS 0.2%

Low (2.9) in cesanta mongoose. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A security vulnerability has been detected in Cesanta Mongoose up to 7.20. This issue affects the function mg_aes_gcm_decrypt of the file /src/tls_aes128.c of the component GCM Authentication Tag Handler. Such manipulation leads to improper verification of cryptographic signature. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is assessed as difficult. The exploit has been disclosed publicly and may be used. Upgrading to version 7.21 is capable of addressing this issue. It is advisable to upgrade the affected component. VulDB has contacted the vendor early and they confirmed quickly, that this issue got fixed already.

Severity

CVSS 4.0

2.9 low
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-04-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-345 Insufficient Verification of Data Authenticity
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-6986 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6986?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6986?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-6986 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cesanta:mongoosefrom 7.0 before 7.21

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13swupdateno fix listedDEBIAN-CVE-2026-6986
Debian14swupdate2025.12+dfsg-10DEBIAN-CVE-2026-6986
Ubuntu25.10, 26.10, Pro:22.04:LTS and 2 moreswupdateno fix listedUBUNTU-CVE-2026-6986

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat rates this vulnerability as Low impact with a CVSS score of 3.7. No Red Hat supported products ship the Cesanta Mongoose library, and the only affected packages are community ones.

The vulnerability is specific to Mongoose's built-in TLS implementation, commonly used in embedded and IoT deployments whilst on Linux distributions applications tend to build against OpenSSL or mbedTLS which are not affected. Even where built-in TLS is in use, an attacker would need an active man-in-the-middle position on the network and prior knowledge of the plaintext layout at specific byte offsets to tamper with data in transit.

The impact is limited to integrity within a single TLS session, with no effect on confidentiality or availability.

Red Hat's mitigation

If you are compiling Mongoose from source, build it against OpenSSL or mbedTLS instead of the built-in TLS stack by setting MG_TLS=MG_TLS_OPENSSL or MG_TLS=MG_TLS_MBED. For applications where switching TLS backends is not an option, restricting network access to the Mongoose service reduces the risk of a man-in-the-middle attack reaching the vulnerable code path.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-6986.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON