CVE-2025-29592: oasys · Path Traversal
Source CVE Database V5
Not known to be exploited · CVSS 5.6 Medium.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2025
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.
What to do
AI-suggested
Given the lack of official patches or detailed remediation guidance, European organizations should take immediate steps to mitigate risk. First, conduct a thorough inventory to identify any deployments of oasys v1.1 and isolate or restrict access to the ProcedureController endpoint, especially from untrusted networks. Implement strict input validation and sanitization at the application or web server level to block directory traversal payloads, such as sequences like '../'. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious path traversal attempts. Monitor logs for anomalous file access patterns or repeated traversal attempts. If possible, upgrade to a newer, patched version of oasys once available or apply vendor-provided workarounds. Limit file system permissions of the application process to the minimum necessary to reduce the impact of any traversal. Conduct penetration testing focused on directory traversal to validate defenses. Finally, maintain heightened monitoring for indicators of compromise and prepare incident response plans tailored to potential exploitation scenarios.
Description
oasys v1.1 is vulnerable to Directory Traversal in ProcedureController.