CVE-2026-126049 · Package
NO FIX YET
Gwenhywfar 5.14.2 frees a nested GWEN_DB node when a BER-TLV record fails to parse, then keeps using it, causing a heap use-after-free in GWEN_TLV_Buffer_To_DB(). An attacker who supplies a constructed TLV record, for example through a malicious chip card read by libchipcard, can corrupt heap memory.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that use Gwenhywfar to parse BER-TLV data, including banking and chip card software built on libchipcard, are exposed when they process untrusted TLV input. Systems that do not parse TLV data through this library can skip it. The sources do not state which versions beyond 5.14.2 are affected or fixed.
Not affected if no-tlv-parsing
Who cares c, gwenhywfar, libchipcard
Unknown from the sources.
No fix yet, per the sources.
Gwenhywfar 5.14.2 contains a heap use-after-free vulnerability in GWEN_TLV_Buffer_To_DB() in src/parser/tlv.c, which frees a nested record's GWEN_DB node when parsing of its contents fails but continues processing and adds the freed node to the parent instead of returning. Attackers can supply a constructed BER-TLV record with unparseable contents, such as via a malicious chip card read by libchipcard, to corrupt heap memory.
This page as .md ·
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.