# CVE-2026-1616: osim: Path Traversal via query parameters in Nginx configuration

> Attackers can perform path traversal via query parameters in the Nginx configuration of Open Security Issue Management, potentially reading unauthorized files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-4mf9-4xp5-f638

## What is CVE-2026-1616?

CVE-2026-1616 is a high-severity path traversal vulnerability in Red Hat osim, published on 29 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The $uri$args concatenation in nginx configuration file present in Open Security Issue Management (OSIM) prior v2025.9.0 allows path traversal attacks via query parameters.

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

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

It affects 1 product.


Products: Redhat Open Security Issue Management.

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

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

## Is CVE-2026-1616 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1616 is a high-severity path traversal vulnerability in Red Hat osim, published on 29 Jan 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-1616 in the wild and no public exploit code.

Affected product: Red Hat osim. 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-1616/ (Markdown: https://insights.sbomify.com/CVE-2026-1616/index.md)
```

## Sources

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

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