# CVE-2026-49145: App::Ack versions through 3.10.0 for Perl read arbitrary files via --files-from in a project .ackrc

> Attackers can read arbitrary files by placing a malicious .ackrc in a repository, causing the ack tool to process unauthorized file paths.

- **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-49145, DEBIAN-CVE-2026-49145, GHSA-c2rv-g977-2fxr, UBUNTU-CVE-2026-49145

## What is CVE-2026-49145?

CVE-2026-49145 is a high-severity path traversal 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 read arbitrary files via --files-from in a project .ackrc.

ack searches up the directory hierarchy from the current directory for a project .ackrc and loads its options. The project-source option blocklist in App::Ack::ConfigLoader does not include --files-from, so a project .ackrc can set it to a path whose listed files ack then reads and searches. Version 3.10.0 added --follow to the blocklist; --files-from remains accepted.

A project .ackrc committed to an untrusted repository can make ack read files outside the project and print their matching lines.

Weakness: CWE-73 (External Control of File Name or Path), CWE-426 (Untrusted Search Path)

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


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

Apply the vendor's patch.

## Is CVE-2026-49145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49145 is a high-severity path traversal 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-49145 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-49145/ (Markdown: https://insights.sbomify.com/CVE-2026-49145/index.md)
```

## Sources

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

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