Inspektor Gadget is a set of tools and framework for data collection and system inspection on Kubernetes clusters and Linux hosts using eBPF. From 0.27.0 until 0.53.1, the uprobe library resolver can allow an unprivileged container to consume excessive CPU and block other containers from starting by supplying a crafted /etc/ld.so.cache file while an uprobe-based gadget is active. The parser in pkg/uprobetracer/ldcache_parser.go trusts EntryCount enough to perform excessive iteration, computes cache1Len with overflowing uint32 arithmetic, and repeatedly calls readStringFromBytes in pkg/uprobetracer/bytes.go, where byte-by-byte immutable string concatenation produces quadratic work. While this processing occurs, pkg/container-hook holds the fanotify container-start pause, allowing a crafted cache to delay startup for roughly a minute, prevent Docker from starting other containers, and degrade monitoring. Processing caches from already-running containers can still consume CPU but does not hold the new-container startup pause, and the advisory establishes no confidentiality or integrity impact. This issue is fixed in version 0.53.1.
CVE-2026-53941
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity69% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026Release v0.53.1
Patch available: inspektor-gadget/inspektor-gadget v0.53.1
https://github.com/inspektor-gadget/inspektor-gadget/releases/tag/v0.53.1commit 2ca55021acf6 (inspektor-gadget/inspektor-gadget)
Fix landed in inspektor-gadget/inspektor-gadget commit 2ca55021acf6 — awaiting tagged release
https://github.com/inspektor-gadget/inspektor-gadget/commit/2ca55021acf675b65040beff2a5ec348054be782[BACKPORT] security hardening fixes for USDT/uprobe ELF/ld.so.cache parsing
Fix merged in inspektor-gadget/inspektor-gadget PR #5547 on 2026-06-02 — awaiting tagged release
https://github.com/inspektor-gadget/inspektor-gadget/pull/5547Uprobe gadgets: unprivileged container's ld.so.cache causes high CPU utilization and container startup DoS · Advisory · inspektor-gadget/inspektor-gadget · GitHub
https://github.com/inspektor-gadget/inspektor-gadget/security/advisories/GHSA-vjhx-2cqw-3q6qVendor Advisories for CVE-2026-53941(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/inspektor-gadget/inspektor-gadget | — | 0.53.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 22:12 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 21:58 UTCEG score recompute
- 2026-09-18 21:44 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 21:29 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 16:58 UTCEG score recompute
- 2026-09-16 15:31 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 18:36 UTCEG score recompute
- 2026-09-15 17:23 UTCEG score recompute▲ 6.90
- 2026-09-15 17:22 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
- 2026-08-19 19:42 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-53941?
When was CVE-2026-53941 disclosed?
Is CVE-2026-53941 actively exploited?
What is the CVSS score of CVE-2026-53941?
How do I remediate CVE-2026-53941?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53941
Is Your Infrastructure Affected by CVE-2026-53941?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.