# CVE-2026-49147: Other in App::Ack

> Attackers can manipulate terminal output via crafted filenames in App::Ack, potentially misleading users or affecting downstream consumers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** ALPINE-CVE-2026-49147, DEBIAN-CVE-2026-49147, GHSA-p4vj-7pqg-xhr6, UBUNTU-CVE-2026-49147

## What is CVE-2026-49147?

CVE-2026-49147 is a high-severity vulnerability in PETDANCE App::Ack, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

App::Ack versions through 3.10.0 for Perl print unsanitised terminal escape sequences from filenames in several output modes.

When ack prints a filename whose basename contains terminal control bytes such as ANSI escape sequences, those bytes reach the terminal unchanged. Version 3.10.0 added a _safe_filename helper that sanitises the filenames printed by -f, -g, the colored match heading, and per-match lines, but the --show-types, -l/-L, and -c paths still emit the raw filename.

A file whose name embeds cursor-movement or color escapes can overwrite or recolor earlier terminal output, or be passed unchanged to a downstream consumer.

Weakness: CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences)

## Which versions are affected by CVE-2026-49147?


## How do I fix CVE-2026-49147?

Upgrade to a fixed version.

## Is CVE-2026-49147 being exploited?

There is no known exploitation of CVE-2026-49147 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49147 and fix it if it is affected.

What it is: CVE-2026-49147 is a high-severity vulnerability in PETDANCE App::Ack, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49147 in the wild and no public exploit code.

Affected product: PETDANCE App::Ack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49147/ (Markdown: https://insights.sbomify.com/CVE-2026-49147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49147
- OSV: https://osv.dev/vulnerability/CVE-2026-49147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49147/
Summaries are generated and may contain mistakes; the official description above is the record.