cve.bz

CVE-2026-126048 Gwenhywfar 4.99.8beta before 5.14.2 Stack Buffer Overflow via GWEN_TLV_Buffer_To_DB()

5.1 mediumEPSS 0.2%

Medium (5.1) in martin preuss gwenhywfar. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Gwenhywfar 4.99.8beta before 5.14.2 contains a stack-based buffer overflow in GWEN_TLV_Buffer_To_DB() in src/parser/tlv.c when decoding BER-TLV tags into a fixed 128-byte buffer. Attackers can supply a record with about 127 or more tag continuation bytes or a truncated multi-byte tag, such as via a malicious chip card's EF_SSD file read by libchipcard's ZKA driver, to crash the application.

Severity

CVSS 4.0

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

CVSS 3.1

4.6 medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126048 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126048?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126048?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-126048 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.

Badge for a README or a site

CVE-2026-126048

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126048](https://cve.bz/cve/badge/CVE-2026-126048.svg)](https://cve.bz/cve/CVE-2026-126048)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126048"><img src="https://cve.bz/cve/badge/CVE-2026-126048.svg" alt="CVE-2026-126048"></a>

Affected

  • martin preuss:gwenhywfar

Versions

From the CNA's record in the CVE List.

ProductAffected
Martin Preuss Gwenhywfarfrom 4.99.8beta before 5.14.2

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON