Strobes VIStrobes VI
CVE DatabaseThreat ActorsResearchAPI Docs
Visit Strobes.coSign Up for Strobes
CVE DatabaseThreat ActorsResearchAPI Docs
Tools
KB Lookup
Visit Strobes.coSign Up for Strobes
HomeCVEs

Do you like the insights?

Strobes vulnerability intelligence is a key component of their Exposure Management platform that helps organizations understand, prioritize, and address security vulnerabilities more effectively.

© 2026 Strobes Security. All rights reserved.
HomeCVEsCVE-2026-24738

CVE-2026-24738

Published: January 27, 2026
Last updated:7 hours ago (January 27, 2026)
Exploit: NoZero-day: NoPatch: YesTrend: Neutral
TL;DR
Updated January 27, 2026

CVE-2026-24738 is a low severity vulnerability with a CVSS score of 0.0. No known exploits currently, and patches are available.

Key Points
  • 1Low severity (CVSS 0.0/10)
  • 2No known public exploits
  • 3Vendor patches are available
Severity Scores
CVSS v30.0
CVSS v20.0
Priority Score0.0
EPSS Score0.0
None
Exploitation LikelihoodMinimal
0.00%EPSS

Very low probability of exploitation

Monitor and patch as resources allow
0.00%
EPSS
0.0
CVSS
No
Exploit
Yes
Patch
Low Priority
no major risk factors

EPSS predicts the probability of exploitation in the next 30 days based on real-world threat data, complementing CVSS severity scores with actual risk assessment.

Description

Unbounded TLV length in ReadFile can cause Denial of Service

Summary

A Denial of Service vulnerability was identified in ReadFile() where unbounded TLV length values could lead to excessive CPU and memory usage when processing data from a malicious or non-compliant NFC source. This issue has been fixed by enforcing strict limits on acceptable TLV lengths.

Affected Versions

  • Affected: All versions prior to v0.17.2
  • Fixed in: v0.17.2

Details

ReadFile() processes BER-TLV encoded data returned from an NFC or APDU source via a Transceiver interface. Prior to the fix, the implementation did not enforce an upper bound on long-form TLV length values.

A malicious or non-compliant NFC endpoint could advertise an excessively large length (up to 4 GB), causing the library to:

  • Perform a very large number of read iterations
  • Allocate excessive memory
  • Consume significant CPU resources
  • Block execution for an extended period

While such lengths are unrealistic for compliant MRTD or ISO 7816 devices, they can be produced by emulated or malicious sources, or by untrusted inputs routed through higher-level APIs.

Impact

Applications using gmrtd to read data from NFC or APDU sources may experience:

  • Excessive CPU usage
  • Memory exhaustion
  • Application hangs or denial of service

No confidentiality or data integrity impact has been identified.

Resolution

This issue has been resolved in v0.17.2.

The fix introduces:

  • Enforcement of maximum allowable TLV lengths
  • Upper bounds on the number of read operations required to retrieve a file
  • Rejection of APDUs that exceed the requested response length

Recommendation

Users should upgrade to v0.17.2 or later.

No additional mitigation is required once the library is updated.

Credits

Discovered and reported by @ramrunner.

CVSS v3 Breakdown
Attack Vector:-
Attack Complexity:-
Privileges Required:-
User Interaction:-
Scope:-
Confidentiality:-
Integrity:-
Availability:-
Patch References
Github.comGithub.com
Trend Analysis
Neutral
Advisories
GitHub Advisory
Cite This Page
APA Format
Strobes VI. (2026). CVE-2026-24738 - CVE Details and Analysis. Strobes VI. Retrieved January 27, 2026, from https://vi.strobes.co/cve/CVE-2026-24738
Quick copy link + title

Please cite this page when referencing data from Strobes VI. Proper attribution helps support our vulnerability intelligence research.