Skip to main content
Menu
CVEs

Mongoose denial of service in TLS certificate date parsing

Affects Mongoose 7.22 up to before 7.24 built with the built-in TLS stack (MG_TLS=1). CVSS scores it 8.2 (high). Fixed in 7.24.

CVE-2026-134170Published , updated

8.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.24
Who is exposed
Not reported

Summary

Cesanta Mongoose's built-in TLS stack has an out-of-bounds read flaw that lets a remote attacker crash the process by presenting a crafted X.509 certificate with an invalid validity month during the TLS handshake. The attack can be carried out over the network without logging in or any user action, and it causes a denial of service.

Written by a model

Original description

Cesanta Mongoose 7.22 before 7.24 with the built-in TLS stack contains an out-of-bounds read in mg_timegm() that allows remote attackers to crash the process via crafted X.509 certificate validity months. Attackers can present a certificate with month '00' or out-of-range values during the handshake, before signature verification, causing an unchecked dm array index and denial of service.

Who should check

Teams running Cesanta Mongoose 7.22 through 7.23 with the built-in TLS stack (MG_TLS=1), such as embedded or networked devices using Mongoose.

“Cesanta Mongoose 7.22 before 7.24 with the built-in TLS stack”

vulncheck.com

What to do

Upgrade to a fixed version: 7.24.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134170 (Cesanta Mongoose 7.22 before 7.24 Out-of-Bounds Read via mg_timegm), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134170 (entry last updated 2026-11-20):
Affected:
- cesanta mongoose: from 7.22, fixed in 7.24
Fixed versions: 7.24.
Conditions (all must be true for the bug to be hit):
- Built-in TLS stack enabled (MG_TLS=1) (source: https://github.com/cesanta/mongoose/security/advisories/GHSA-wc32-gjw7-5g65)
- Mongoose version 7.22 up to before 7.24 (source: https://www.vulncheck.com/advisories/cesanta-mongoose-7.22-before-7.24-out-of-bounds-read-via-mg-timegm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134170 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134170 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/cesanta/mongoose/security/advisories/GHSA-wc32-gjw7-5g65
- https://github.com/cesanta/mongoose/commit/7fccc2b75f64f416ba1c7fd4f5072ae33b44d578
- https://github.com/cesanta/mongoose/releases/tag/7.24
- https://github.com/cesanta/mongoose/blob/7.23/src/util.c#L14-L25
- https://github.com/cesanta/mongoose/blob/7.23/src/tls_builtin.c#L1407-L1423
- https://www.vulncheck.com/advisories/cesanta-mongoose-7.22-before-7.24-out-of-bounds-read-via-mg-timegm
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134170
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134170"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.2/10CVSS 8.2
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 8

Questions about CVE-2026-134170

Is CVE-2026-134170 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A crafted X.509 certificate can make the Mongoose process read outside its buffer, which crashes the process as a denial of service. On 32-bit targets the read may also leak memory.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-134170?

mongoose: from 7.22 before 7.24.

Source: cve.now feed data

Am I affected, and how do I check?

Mongoose versions from 7.22 up to, but not including, 7.24 that use the built-in TLS stack, enabled with MG_TLS=1. To check, confirm the Mongoose version in use and whether MG_TLS=1 is set in the build.

Source: github.com, vulncheck.com

How do I fix CVE-2026-134170?

Upgrade Mongoose to version 7.24 or later.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.