dbcve.org
CWE-150Weakness · CWE-150

CVE-2026-49147

HIGH · 7.5 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

App::Ack versions through 3.10.0 print filenames containing terminal control characters (ANSI escape sequences) without sanitization in three output modes: --show-types, -l/-L, and -c. While version 3.10.0 added a _safe_filename helper to sanitize filenames in other modes, these three modes remain vulnerable, allowing malicious filenames to manipulate terminal display or inject content into downstream processes.

MitigationApply vendor patch or upgrade to a version after 3.10.0 that sanitizes all filename output modes, or implement pre-processing to filter/escape control characters from filenames before ack processes them.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed App::Ack version
    Run `ack --version` or `ack --help` to see the version number
    Affected if Version is 3.10.0 or earlier
  2. Identify if vulnerable output modes are used
    Review command-line invocations of ack for any use of --show-types, -l, -L, or -c flags
    Affected if Any of these flags are used in ack commands
  3. Check for potential malicious filenames in search paths
    Inspect the directories being searched by ack for filenames containing ANSI escape sequences (look for unusual characters, use `ls -la` or `find` to list files)
    Affected if Filenames with control characters exist and are processed by the vulnerable output modes
  4. Verify if _safe_filename is not applied to the output mode
    Review the App::Ack source code if accessible, or test by creating a test file with ANSI characters and running ack with -l or --show-types to observe raw output
    Affected if The output shows unescaped ANSI sequences instead of escaped/sanitized versions

You are affected if you use App::Ack version 3.10.0 or earlier and employ the --show-types, -l, -L, or -c output flags on directories containing filenames with terminal control characters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch or upgrade to a version after 3.10.0 that sanitizes all filename output modes, or implement pre-processing to filter/escape control characters from filenames before ack processes them.

Recommended fix Moderate confidence

Latest stable App::Ack release (version > 3.10.0)

  1. 1. Check your current App::Ack version by running: ack --version
  2. 2. Upgrade to the latest stable release of App::Ack using your Perl module installer (e.g., cpan -T App::Ack or cpanm App::Ack)
  3. 3. Verify the upgrade was successful: ack --version
  4. 4. Test that filenames with escape sequences are properly sanitized in all output modes (-f, -g, -l, -L, -c, --show-types)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49147 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data