LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24738: gmrtd ReadFile Vulnerable to Denial of Service via Excessive TLV Length Values

gmrtd is a Go library for reading Machine Readable Travel Documents (MRTDs). Prior to version 0.17.2, ReadFile accepts TLVs with lengths that can range up to 4GB, which can cause unconstrained resource consumption in both memory and cpu cycles. ReadFile can consume an extended TLV with lengths well outside what would be available in ICs. It can accept something all the way up to 4GB which would take too many iterations in 256 byte chunks, and would also try to allocate memory that might not be available in constrained environments like phones. Or if an API sends data to ReadFile, the same problem applies. The very small chunked read also locks the goroutine in accepting data for a very large number of iterations. projects using the gmrtd library to read files from NFCs can experience extreme slowdowns or memory consumption. A malicious NFC can just behave like the mock transceiver described above and by just sending dummy bytes as each chunk to be read, can make the receiving thread unresponsive and fill up memory on the host system. Version 0.17.2 patches the issue.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24738 affects applications using the Go gmrtd library before 0.17.2 to read electronic travel documents. A malicious or abnormal NFC source can claim an excessively large file length, causing the app to waste CPU and memory. The main business impact is denial of service, especially on constrained devices such as phones.

Executive priority

Treat as a targeted availability risk, not a data-theft issue. Remediate during the next dependency update cycle, faster for customer-facing, mobile, kiosk, or operational identity systems where reader unresponsiveness could disrupt service.

Technical view

gmrtd ReadFile accepted TLV length values up to about 4GB before version 0.17.2. This can trigger unconstrained allocation and many small 256-byte read iterations, locking a goroutine and consuming resources. The issue maps to CWE-400 and CWE-770 and is scored CVSS 4.0 5.9 with high availability impact.

Likely exposure

Exposure is limited to projects that depend on gmrtd versions earlier than 0.17.2 and pass NFC or API-supplied MRTD file data into ReadFile. Systems not using gmrtd, or not processing untrusted MRTD/NFC-like data through ReadFile, are not indicated as affected by the provided sources.

Exploitation context

The advisory describes a malicious NFC or API-supplied data source causing excessive reads and memory consumption. The CVE is not marked KEV, and the provided sources do not state active exploitation in the wild. User interaction or proximity conditions are reflected in the CVSS vector.

Researcher notes

The public advisory attributes the flaw to excessive TLV length handling in ReadFile. The patch is released in v0.17.2 and linked to commit 54469a95e5a20a8602ac1457b2110bfeb80c8891. Evidence supports denial of service only; no confidentiality or integrity impact is described.

Mitigation direction

  • Upgrade gmrtd to version 0.17.2 or later.
  • Prioritize mobile, kiosk, border, or identity workflows using NFC MRTD reads.
  • If immediate upgrade is blocked, review vendor guidance and reduce exposure to untrusted inputs.

Validation and detection

  • Inventory Go modules for github.com/gmrtd/gmrtd versions below 0.17.2.
  • Confirm whether application code calls ReadFile on NFC or API-supplied MRTD data.
  • Verify deployed builds include gmrtd 0.17.2 or the referenced fixing commit.
  • Monitor affected applications for abnormal memory growth or reader thread unresponsiveness.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24738 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 4.0MediumCVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.9Medium
CVSS 4.0 vector shape for CVE-2026-24738Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gmrtdgmrtd< 0.17.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.