CVE-2025-13875VulnerabilityPublished 2 Dec 2025

CVE-2025-13875: Yohann0617 oci-helper · Path Traversal

Affects Yohann0617 oci-helperSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Dec 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 2026-10-25.

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 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

Affected software

Product	Affected	Fixed in
GitHubyohann0617/oci-helper`pkg:github/yohann0617/oci-helper`Other threats	Affected =3.2.0 =3.2.1 =3.2.2 =3.2.3 =3.2.4	Fixed in–

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

AI-suggested

Immediate mitigation steps include restricting network access to the oci-helper service to trusted administrators only, implementing strict file system permissions to limit the scope of accessible files, and monitoring logs for unusual file access patterns indicative of path traversal attempts. Organizations should conduct thorough audits of systems running vulnerable versions and isolate them if possible. Employing application-layer firewalls or intrusion detection systems with custom rules to detect path traversal payloads can help detect exploitation attempts. Until official patches are released, consider deploying compensating controls such as containerization or sandboxing of the oci-helper process to limit potential damage. Regularly check for vendor updates or community patches and apply them promptly. Additionally, educating system administrators about the risks and signs of exploitation can improve early detection and response.

Description

A weakness has been identified in Yohann0617 oci-helper up to 3.2.4. This issue affects the function addCfg of the file src/main/java/com/yohann/ocihelper/service/impl/OciServiceImpl.java of the component OCI Configuration Upload. Executing manipulation of the argument File can lead to path traversal. It is possible to launch the attack remotely. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized disclosure of sensitive configuration files or system data, impacting confidentiality and integrity. Organizations using oci-helper in their cloud infrastructure management or container orchestration pipelines may face risks of lateral movement or privilege escalation if attackers leverage this flaw. Although the impact on availability is low, the breach of sensitive configuration data could undermine trust and compliance with data protection regulations such as GDPR. The lack of vendor response and patches increases the window of exposure. Industries with critical cloud deployments, such as finance, healthcare, and manufacturing, could be particularly affected. The medium severity rating suggests moderate risk, but the potential for escalation or chaining with other vulnerabilities could increase the overall threat level.

Summary

CVE-2025-13875 identifies a path traversal vulnerability in the oci-helper utility developed by Yohann0617, specifically in versions 3.2.0 through 3.2.4. The vulnerability resides in the addCfg function within the OCI Configuration Upload component, implemented in the OciServiceImpl.java source file. This flaw allows an attacker to manipulate the file argument passed to the function, enabling traversal outside the intended directory structure. Such manipulation can lead to unauthorized reading or potentially overwriting of arbitrary files on the host system. The attack vector is remote, requiring no user interaction, but does require low-level privileges (PR:L) on the system. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, and low impact on confidentiality, integrity, and availability. Although the vendor was notified early, they have not issued any patches or advisories, and no known exploits have been observed in the wild yet. The availability of proof-of-concept exploit code increases the risk of future exploitation. This vulnerability is particularly concerning for environments that rely on oci-helper for managing OCI configurations, as it could allow attackers to access sensitive configuration files or system files, potentially leading to further compromise.

References

Community reviews

Loading reviews…