Inspektor Gadget uses unsanitized ANSI Escape Sequences In columns Output Mode

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-25996: 0.64% estimated exploitation activity in the next 30 days; percentile 50.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description String fields from eBPF events in columns output mode are rendered to the terminal without any sanitization of control characters or ANSI escape sequences. Therefore, a maliciously forged – partially or completely – event payload, coming from an observed container, might inject the escape sequences into the terminal of ig operators, with various effects. The columns output mode is the default when running ig run interactively. PoC Attachments run.sh escapeinject.c 1. Setup a Linux host and build/install ig version 0.48.0 2. Run the attached run.sh on a terminal 3. Run sudo ig run traceopen -c poc-escape-inject on another terminal 4. Press "Enter" on the terminal attached to run.sh 5. Observe the events traced by ig 6. Notice that, at some point, the line where /etc/shadow is logged is overwritten /etc/bashrc, demonstrating the log injection Impact The impact depends on the injection point – mostly due to length limitations – and on the terminal used by the operator when…

Published by the source

22 Apr 2026, 18:50 UTC

Last modified by the source

22 Apr 2026, 18:50 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-34r5-6j7w-235f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25996

Advisory: Inspektor Gadget uses unsanitized ANSI Escape Sequences In `columns` Output Mode
IDs: CVE-2026-25996, GHSA-34r5-6j7w-235f
Record: https://patchnext.com/advisories/cve-2026-25996 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/inspektor-gadget/inspektor-gadget 0.49.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/inspektor-gadget/inspektor-gadget: affected < 0.49.1; fixed in 0.49.1

## Suggested inspection (read-only)
- Go github.com/inspektor-gadget/inspektor-gadget: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/inspektor-gadget/inspektor-gadget.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-34r5-6j7w-235f (GitHub-reviewed advisory GHSA-34r5-6j7w-235f lists affected ranges: Go github.com/inspektor-gadget/inspektor-gadget >=0 <0.49.1)

Commands are suggestions: review each one before running it.