CVE-2026-112015 — Omnigent 0.3.0 before 0.14.0 Path Traversal via Sub-Agent os_env.cwd
Omnigent 0.3.0 before 0.14.0 contains a path traversal vulnerability that allows authenticated users to escape the workspace by setting os_env.cwd on nested sub-agents. Attackers can upload a bundle whose sub-agent uses an absolute or parent-traversing working directory, bypassing root-only validation in bundles.py, to read and write host files as the runner user.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+6
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Omnigent-ai Omnigent).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Omnigent-ai | Omnigent | ≥ 0.3.0 and < 0.14.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.7 | CVSS 4.0 | High | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 7.7 | CVSS 4.0 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 7.5 | CVSS 3.1 | High | 1.6 | 5.9 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.5 | CVSS 3.1 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Deferred
- Affected products added · omnigent-ai/omnigent
- SSVC assessment updated
- Record published
- CVSS changed · 7.5
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 18, 2026 – Oct 18, 2026
- 1× Official description updated · Oct 18, 2026 – Oct 18, 2026
References
7 on the record
- github.com/omnigent-ai/omnigent/commit/4a406d5b3b3f3a7c3401eab659ab04e728923b94
- github.com/omnigent-ai/omnigent/releases/tag/v0.14.0
- github.com/advisories/GHSA-vg9j-3mjv-5cq3
- www.vulncheck.com/advisories/omnigent-0.3.0-before-0.14.0-path-traversal-via-sub-agent-
- github.com/omnigent-ai/omnigent/security/advisories/GHSA-p5x3-3gqh-x44g
- github.com/omnigent-ai/omnigent/blob/v0.13.0/omnigent/server/bundles.py
- nvd.nist.gov/vuln/detail/CVE-2026-112015
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-62677 Omnigent: Unvalidated os_env.cwd in agent bundle yields arbitrary host filesystem access on runners without OMNIGENT_RUNNER_WORKSPACE Aug 21, 2026
- Critical CVE-2026-62674 Omnigent: Shared Agent Bundle Overwrite Leads to Authenticated Runner RCE Aug 21, 2026
- High CVE-2026-62675 Omnigent: Uploaded Agent Bundle Allows Authenticated Runner RCE via Python Callable Tools Aug 21, 2026
- High CVE-2026-62676 Omnigent Guardrail policy bypass: shell-command parser fails open in policies/builtins/_shell.py Aug 21, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-112015 is "Omnigent 0.3.0 before 0.14.0 Path Traversal via Sub-Agent os_env.cwd", rated High. It affects Omnigent (Omnigent-ai); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.45% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.