[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fx7hZxmpu1JJ8QPNCA2S5BxJAkAdh37wsiN7iET_xMKc":3},{"article":4,"iocs":38,"iocs_total":43,"watch_terms":44,"solutions":45,"lesson":132},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":25,"category":26,"article_tags":30},"a79f1f83-8b7c-48e9-b1e1-80e84a52b627","GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP Keys","gnupg-warns-critical-gpgme-flaw-could-expose-app-data-via-malicious-openpgp-keys-3b426a","A malicious OpenPGP key with an unusually long user ID can trigger a critical memory bug in GPGME, the standard library that programs use to work with GnuPG. The GnuPG project warned yesterday that the flaw could be used to steal data from affected applications and has released fixed versions. The bug, tracked as CVE-2026-129975, affects all software that uses GPGME before version 2.3.0,","A critical memory bug in the GPGME library, tracked as CVE-2026-129975, can be triggered by a malicious OpenPGP key with an unusually long user ID. This flaw could potentially lead to data theft from affected applications, and remote code execution cannot be ruled out. GnuPG has released fixed versions of GPGME (2.3.1) and related packages like Gpg4win (5.1.2).","GnuPG warns of critical GPGME flaw that could expose app data via malicious OpenPGP keys.","https:\u002F\u002Fthehackernews.com\u002F2026\u002F11\u002Fgnupg-warns-critical-gpgme-flaw-could.html","https:\u002F\u002Fblogger.googleusercontent.com\u002Fimg\u002Fb\u002FR29vZ2xl\u002FAVvXsEiTmX4ayWzvM0EzPttZ610B2837FppeU5AEmQmztLH2lai78EDQtjrp4wVI_bubSe2c2NGBE5sqBT9Py1mKkHQKN2faBkOzU70d7FntrpYD7Et2eeBxLNy2gzByAo1i8Aaw_VMBZD62RnBMY2md3iNfegK9M_NR5qTRDBw8s0uwKy1w7JoTV0zkDS_17Lse\u002Fs1600\u002Fpgp.jpg","2026-11-21T11:05:53+00:00","2026-11-21T12:00:20.754465+00:00",8,[17,20,23],{"name":18,"type":19},"GPGME","product",{"name":21,"type":22},"GnuPG","vendor",{"name":24,"type":19},"Gpg4win","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":25,"icon":27,"name":28,"slug":29},null,"Vulnerabilities","vulnerabilities",[31,33],{"category":32},{"id":25,"icon":27,"name":28,"slug":29},{"category":34},{"id":35,"icon":27,"name":36,"slug":37},"ade75414-7914-4e23-a450-48b64546ee70","Open Source","open-source",[39],{"type":40,"value":41,"context":42},"cve","CVE-2026-129975","GPGME memory bug identifier",1,[21,18,24],{"controls":46,"vendors":131},[47,76,105],{"slug":48,"name":49,"problem":50,"products":51},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[52,60,68],{"vendor_slug":53,"vendor_name":54,"vendor_logo":55,"product_slug":56,"product_name":57,"url":58,"description":59},"rapid7","Rapid7","\u002Fvendor-logos\u002Frapid7.png","insightvm","Rapid7 Exposure Command (InsightVM)","https:\u002F\u002Fwww.rapid7.com\u002Fproducts\u002Finsightvm\u002F","Vulnerability scanning and risk-based prioritisation; InsightVM is now part of Exposure Command, alongside attack surface and cloud risk.",{"vendor_slug":61,"vendor_name":62,"vendor_logo":63,"product_slug":64,"product_name":65,"url":66,"description":67},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"vendor_slug":69,"vendor_name":70,"vendor_logo":71,"product_slug":72,"product_name":73,"url":74,"description":75},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"slug":77,"name":78,"problem":79,"products":80},"patch-management","Automated patch management","Known holes get closed in days, not months.",[81,89,97],{"vendor_slug":82,"vendor_name":83,"vendor_logo":84,"product_slug":85,"product_name":86,"url":87,"description":88},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"vendor_slug":90,"vendor_name":91,"vendor_logo":92,"product_slug":93,"product_name":94,"url":95,"description":96},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",{"vendor_slug":98,"vendor_name":99,"vendor_logo":100,"product_slug":101,"product_name":102,"url":103,"description":104},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"slug":106,"name":107,"problem":108,"products":109},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",[110,118,123],{"vendor_slug":111,"vendor_name":112,"vendor_logo":113,"product_slug":114,"product_name":115,"url":116,"description":117},"dataminr","Dataminr","\u002Fvendor-logos\u002Fdataminr.png","agentic-threat-intelligence-platform","Agentic Threat Intelligence Platform","https:\u002F\u002Fwww.dataminr.com\u002Fproducts\u002Fcyber-defense\u002Fagentic-threat-intelligence-platform\u002F","Threat intelligence platform, formerly ThreatConnect TI Ops, that collects, scores and structures intelligence and pushes it into security tools.",{"vendor_slug":111,"vendor_name":112,"vendor_logo":113,"product_slug":119,"product_name":120,"url":121,"description":122},"dataminr-threat-intelligence","Dataminr Threat Intelligence","https:\u002F\u002Fwww.dataminr.com\u002Fproducts\u002Fcyber-defense\u002Fthreat-intelligence\u002F","Real-time alerts on emerging cyber threats, exploited vulnerabilities and attacks relevant to your organisation, detected with AI across a large set of public data sources.",{"vendor_slug":124,"vendor_name":125,"vendor_logo":126,"product_slug":127,"product_name":128,"url":129,"description":130},"reliaquest","ReliaQuest","\u002Fvendor-logos\u002Freliaquest.png","greymatter-digital-risk-protection","GreyMatter Digital Risk Protection","https:\u002F\u002Freliaquest.com\u002Fsecurity-operations-platform\u002Fdark-web-and-digital-risk-protection\u002F","Watches the open, deep and dark web for threats aimed at an organisation and alerts its security team in real time.",[],{"slug":133,"title":134,"body":135,"framework_refs":136,"framework_notes":142},"critical-gpgme-memory-bug-exploitable-via-malicious-openpgp-keys","Critical GPGME Memory Bug Exploitable via Malicious OpenPGP Keys","A critical memory corruption vulnerability (CVE-2026-129975) in the GPGME library allows an attacker to trigger a flaw simply by supplying a malicious OpenPGP key with an unusually long user ID, requiring no authentication or privileged access. This type of input-validation failure in a widely-used cryptographic library is particularly dangerous because GPGME underpins many applications that handle sensitive encrypted data. If exploited, attackers could steal application data or potentially achieve remote code execution. The fact that GnuPG has already released patched versions (GPGME 2.3.1, Gpg4win 5.1.2) means the primary risk now lies with organizations that delay applying these updates.",[137,138,139,140,141],"CIS Control 7: Continuous Vulnerability Management (v8)","CIS Control 2: Inventory and Control of Software Assets (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 ID.AM-05: Assets are prioritized based on classification, criticality, resources, and impact","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(e)":143,"NIST SP 800-53 SI-2: Flaw Remediation":144,"CIS Control 7: Continuous Vulnerability Management (v8)":145,"CIS Control 2: Inventory and Control of Software Assets (v8)":146,"NIST CSF 2.0 ID.AM-05: Assets are prioritized based on classification, criticality, resources, and impact":147},"NIS2 Article 21(2)(e) covers security in acquisition, development and maintenance including vulnerability handling and disclosure, requiring entities to have processes that ensure third-party library vulnerabilities like this GPGME flaw are addressed in a timely manner.","SI-2 explicitly requires organizations to identify, report, and correct information system flaws, and to install security-relevant updates within organizationally defined time periods—directly addressing the need to apply the GPGME patch promptly.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities in software; had a mature vulnerability management program been in place, the GPGME dependency would have been flagged and patched upon CVE publication.","CIS Control 2 demands an accurate inventory of all software in use, which is a prerequisite for identifying every application that depends on GPGME and ensuring none are missed during patching.","Knowing that GPGME is a critical cryptographic dependency and prioritizing it accordingly would have accelerated patch deployment before exploitation could occur."]