CVE-2026-112015 omnigent-ai CVE debrief

Who should care

Defenders responsible for Omnigent deployments should assess exposure and apply patches or mitigations to prevent potential file system access. This includes verifying the affected versions, restricting access to authenticated users, and monitoring for suspicious activity. Additionally, defenders should review compensating controls for exposed systems while remediation is scheduled and verified, and track exceptions, retest remediated assets, and close the

Why it matters

CVE-2026-112015 is a path traversal vulnerability in Omnigent that allows authenticated users to access and modify host files. Defenders should verify exposure, apply patches, and restrict access to prevent potential security consequences.

• Potential file system access as the runner user
• Bypassing of root-only validation in bundles.py
• Possible read and write access to host files

Technical summary

The vulnerability allows authenticated users to escape the workspace by setting os_env.cwd on nested sub-agents, bypassing root-only validation in bundles.py. This enables attackers to read and write host files as the runner user, potentially leading to unauthorized file system access. The vulnerability is caused by a lack of proper validation in the bundles.py file, which allows attackers to manipulate the working directory of nested sub-agents. To exploit this vulnerability, attackers would need to upload a bundle whose sub-agent uses an absolute or parent-traversing working directory.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or mitigations to prevent potential file system access.

Recommended defensive actions

• Verify Omnigent version and check for patches or updates
• Restrict access to authenticated users and monitor for suspicious activity
• Implement additional security controls to prevent file system access
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional verification is needed to confirm affected versions and scope. The vulnerability is caused by a lack of proper validation in the bundles.py file, which allows attackers to manipulate the working directory of nested sub-agents. Defenders should verify the affected versions and apply patches or mitigations to prevent potential file system access. The CVE record and NVD entry provide some information, but further review of the Omnigent codebase and testing,

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.