# CVE-2025-34176: Netgate pfSense CE Suricata Package v7.0.8_2 Directory Traversal Information Disclosure

> Authenticated attackers can enumerate files on pfSense CE via directory traversal in the Suricata package, revealing file existence without reading contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-4fgr-95mh-x7h2

## What is CVE-2025-34176?

CVE-2025-34176 is a medium-severity path traversal vulnerability in Netgate pfSense CE, published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In pfSense CE /suricata/suricata_ip_reputation.php, the value of the iplist parameter is not sanitized of directory traversal-related strings/characters. This value is directly used in a file existence check operation. While the contents of the file cannot be read, the server reveals whether the file exists, which enables an attacker to enumerate files on the target. The attacker must be authenticated with at least "WebCfg - Services: suricata package" permissions.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-34176?

It affects 1 product.


Products: Pfsense Pfsense.

## How do I fix CVE-2025-34176?

No fix has been published for CVE-2025-34176 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34176 being exploited?

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

## Other vulnerabilities in Netgate pfSense CE

- [CVE-2025-69691](https://insights.sbomify.com/CVE-2025-69691/): Code injection in n/a (critical 9.9)
- [CVE-2023-29974](https://insights.sbomify.com/CVE-2023-29974/): Weak cryptography in n/a (critical 9.8)
- [CVE-2025-69690](https://insights.sbomify.com/CVE-2025-69690/): Deserialization in n/a (critical 9.1)
- [CVE-2021-41282](https://insights.sbomify.com/CVE-2021-41282/): Code injection in n/a (high 8.8)
- [CVE-2016-10709](https://insights.sbomify.com/CVE-2016-10709/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34176 and fix it if it is affected.

What it is: CVE-2025-34176 is a medium-severity path traversal vulnerability in Netgate pfSense CE, published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34176 in the wild and no public exploit code.

Affected product: Netgate pfSense CE. 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-2025-34176/ (Markdown: https://insights.sbomify.com/CVE-2025-34176/index.md)
```

## Sources

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

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