# CVE-2025-49830: Path traversal in conjur

> Authenticated attackers can exploit a YAML parser flaw to read arbitrary files on the server, enabling reconnaissance and data disclosure.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/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:** 15 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-7m6h-fqrm-m9c5

## What is CVE-2025-49830?

CVE-2025-49830 is a high-severity path traversal vulnerability in cyberark conjur, published on 15 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Conjur provides secrets management and application identity for infrastructure. An authenticated attacker who is able to load policy can use the policy yaml parser to reference files on the Secrets Manager, Self-Hosted server. These references may be used as reconnaissance to better understand the folder structure of the Secrets Manager/Conjur server or to have the yaml parser include files on the server in the yaml that is processed as the policy loads. This issue affects Secrets Manager, Self-Hosted (formerly Conjur Enterprise) prior to versions 13.5.1 and 13.6.1 and Conjur OSS prior to version 1.22.1. Conjur OSS version 1.22.1 and Secrets Manager, Self-Hosted versions 13.5.1 and 13.6.1 fix the issue.

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

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

It affects 1 product.


Products: Cyberark Conjur.

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

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

## Is CVE-2025-49830 being exploited?

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

## Other vulnerabilities in cyberark conjur

- [CVE-2025-49827](https://insights.sbomify.com/CVE-2025-49827/): Conjur OSS and Secrets Manager, Self-Hosted (formerly Conjur Enterprise) Vulnerable to Bypass of IAM Authenticator (critical 9.1)
- [CVE-2025-49831](https://insights.sbomify.com/CVE-2025-49831/): Auth bypass in conjur (critical 9.1)
- [CVE-2025-49828](https://insights.sbomify.com/CVE-2025-49828/): Conjur OSS and Secrets Manager, Self-Hosted (formerly Conjur Enterprise) Vulnerable to Remote Code Execution (high 8.6)
- [CVE-2025-49829](https://insights.sbomify.com/CVE-2025-49829/): Conjur OSS and Secrets Manager, Self-Hosted (formerly Conjur Enterprise) missing validations (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49830 is a high-severity path traversal vulnerability in cyberark conjur, published on 15 Jul 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-49830 in the wild and no public exploit code.

Affected product: cyberark conjur. 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-49830/ (Markdown: https://insights.sbomify.com/CVE-2025-49830/index.md)
```

## Sources

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

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