How severe is GHSA-j49h-6577-5xwq?

No CVSS score has been assigned to GHSA-j49h-6577-5xwq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j49h-6577-5xwq?

GHSA-j49h-6577-5xwq affects the following packages: github.com/gmrtd/gmrtd (Go). Ecosystems affected: Go.

How do I fix GHSA-j49h-6577-5xwq?

Update github.com/gmrtd/gmrtd to 0.17.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j49h-6577-5xwq is resolved across your whole dependency graph.

How do I detect GHSA-j49h-6577-5xwq in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gmrtd/gmrtd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j49h-6577-5xwq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-j49h-6577-5xwq?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j49h-6577-5xwq can be triaged on real exposure rather than presence alone.

Is GHSA-j49h-6577-5xwq actively exploited in the wild?

No public exploit code has been indexed for GHSA-j49h-6577-5xwq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j49h-6577-5xwq?

GHSA-j49h-6577-5xwq has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j49h-6577-5xwq?

GHSA-j49h-6577-5xwq is classified as Uncontrolled Resource Consumption (CWE-400), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j49h-6577-5xwq published, and has it been updated?

GHSA-j49h-6577-5xwq was published on January 27, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-j49h-6577-5xwq — gmrtd

Fix: gmrtd/gmrtd@54469a9

GHSA-j49h-6577-5xwq is a Uncontrolled Resource Consumption vulnerability in github.com/gmrtd/gmrtd. A fix is available for github.com/gmrtd/gmrtd — see the affected versions and patch details below.

gmrtd ReadFile Vulnerable to Denial of Service via Excessive TLV Length Values

Also known asCVE-2026-24738GO-2026-4379

Published

Jan 27, 2026

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j49h-6577-5xwq.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/gmrtd/gmrtd

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/gmrtd/gmrtd`	all versions	0.17.2`go get github.com/gmrtd/gmrtd@v0.17.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gmrtd/gmrtd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/gmrtd/gmrtd to 0.17.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j49h-6577-5xwq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j49h-6577-5xwq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-j49h-6577-5xwq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# 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

O3 Security · Impact-Aware SCA

Is GHSA-j49h-6577-5xwq in your dependencies?

O3 Security finds GHSA-j49h-6577-5xwq across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works