Omnigent: Uploaded Agent Bundle Allows Authenticated Runner RCE via Python Callable Tools

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-62675: 0.65% estimated exploitation activity in the next 30 days; percentile 51.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary An authenticated user can upload a crafted agent bundle that defines a server-side Python callable tool. The server validates the uploaded bundle, but it does not block dangerous callable: paths in untrusted user-provided agent configs. When the tool is invoked, the runner imports and executes that Python callable. A crafted bundle can point the tool at subprocess.checkoutput, which lets the attacker run a local command on the runner machine. This is serious because hosted Omnigent deployments can have multiple users and shared or managed runner hosts. A normal logged-in user should not be able to make the runner execute arbitrary local commands. Details The uploaded bundle path is reachable through session creation. Omnigent supports custom agent bundles through multipart POST /v1/sessions; the Web UI uses this same endpoint for custom agents: Create custom agent builds and uploads a bundle \ createBundledSession posts the bundle to /v1/sessions A crafted bundle can also be…

Published by the source

2 Sep 2026, 21:54 UTC

Last modified by the source

2 Sep 2026, 21:54 UTC

Source last checked

26 Oct 2026, 13:51 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-756x-9hf6-q4h4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-62675

Advisory: Omnigent: Uploaded Agent Bundle Allows Authenticated Runner RCE via Python Callable Tools
IDs: CVE-2026-62675, GHSA-756x-9hf6-q4h4
Record: https://patchnext.com/advisories/cve-2026-62675 (revision 1, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: omnigent 0.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI omnigent: affected < 0.3.0; fixed in 0.3.0

## Suggested inspection (read-only)
- `python -m pip show omnigent`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on omnigent.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-756x-9hf6-q4h4 (GitHub-reviewed advisory GHSA-756x-9hf6-q4h4 lists affected ranges: PyPI omnigent >=0 <0.3.0)

Commands are suggestions: review each one before running it.