VulnerabilityPublished 29 Jan 2026

CVE-2026-1616: Red Hat osim · Path Traversal

Affects Red Hat osimSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to v2025.9.0 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in v2025.9.0, 2025.9.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade osim to v2025.9.0; redhatproductsecurity/osim and osim to 2025.9.0.

Affected software

Product	Affected	Fixed in
Red Hatosim	Affected <2025.9.0	Fixed in v2025.9.0
GitHubredhatproductsecurity/osim`pkg:github/redhatproductsecurity/osim`Other threats	Affected <2025.9.0	Fixed in 2025.9.0
GitHubosim`pkg:github/osim`Other threats	Affected <2025.9.0	Fixed in 2025.9.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade OSIM to version 2025.9.0 or later as soon as possible once available to ensure the vulnerability is patched.
Review and harden nginx configuration files to avoid unsafe concatenation of $uri and $args variables; consider using secure methods to sanitize and validate input parameters.
Implement strict access controls on the filesystem to limit the web server's ability to read sensitive directories and files outside the intended scope.
Employ web application firewalls (WAFs) with rules designed to detect and block path traversal attempts targeting query parameters.
Conduct regular security audits and penetration testing focused on web server configurations and input validation mechanisms.
Monitor network traffic and logs for unusual access patterns or attempts to exploit path traversal vectors.
Isolate OSIM deployments behind VPNs or internal networks where feasible to reduce exposure to unauthenticated remote attacks.
Educate system administrators on secure configuration practices for nginx and related components.

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.

Impact

For European organizations, this vulnerability can lead to unauthorized disclosure of sensitive information managed by OSIM, including security issue data and internal reports. Confidentiality breaches could expose critical vulnerability management details, potentially aiding further attacks. Organizations in sectors such as finance, government, and critical infrastructure that rely on Red Hat OSIM for security issue tracking are particularly at risk. The lack of integrity or availability impact limits the scope to data exposure rather than system disruption. However, the sensitive nature of the data involved elevates the risk profile. The remote, unauthenticated exploit vector increases the attack surface, especially for publicly accessible OSIM deployments. This could lead to compliance violations under GDPR if personal or sensitive data is exposed. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, emphasizing the need for proactive mitigation.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/RedHatProductSecurity/osim/pull/615 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jan 2026, 14:27 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats