# CVE-2025-13491: IBM App Connect Enterprise Certified Container Information Disclosure

> An attacker can access sensitive files or modify configurations in IBM App Connect Enterprise Certified Container due to an untrusted search path vulnerability.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-f4xv-648j-g6xj

## What is CVE-2025-13491?

CVE-2025-13491 is a medium-severity path traversal vulnerability in IBM App Connect Enterprise Certified Container, published on 5 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM App Connect Enterprise Certified Container CD: 11.2.0 through 11.6.0, 12.1.0 through 12.19.0 and 12.0 LTS: 12.0.0 through 12.0.19 could allow an attacker to access sensitive files or modify configurations due to an untrusted search path.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2025-13491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13491 is a medium-severity path traversal vulnerability in IBM App Connect Enterprise Certified Container, published on 5 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13491 in the wild and no public exploit code.

Affected product: IBM App Connect Enterprise Certified Container. 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-13491/ (Markdown: https://insights.sbomify.com/CVE-2025-13491/index.md)
```

## Sources

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

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