CVE-2026-62675: Omnigent Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-756x-9hf6-q4h4
CVSS 8.8
CWE-94
Published
Advisory Summary

CVE-2026-62675 is a HIGH (CVSS 8.8) remote code execution vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting Omnigent libraries in the PyPI ecosystem. The issue involves uploaded agent bundle allows authenticated runner rce via python callable tools. Remediation is available by upgrading affected packages to version 0.3.0.

CVE-2026-62675 at a Glance

CVE Identifier CVE-2026-62675
GHSA Identifier GHSA-756x-9hf6-q4h4
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product Omnigent
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-62675

To remediate this vulnerability, upgrade all affected Omnigent dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

omnigent fixed: 0.3.0
pip install omnigent>=0.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show omnigent

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-62675, inspect your installed packages using pip:

pip show omnigent

Analyze the terminal output to locate any version of Omnigent in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.3.0), your application is affected.

Note: The pip show omnigent command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In Omnigent, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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.check_output`, 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](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/ap-web/src/shell/NewChatDialog.tsx#L1265-L1277) \ [`createBundledSession` posts the bundle to `/v1/sessions`](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/ap-web/src/lib/sessionsApi.ts#L421-L460) A crafted bundle can also be submitted directly through the API/CLI when creating a session from agent YAML. The PoC below uses this direct bundle shape so the vulnerable trust boundary is easy to reproduce. On the server, uploaded bundles are validated here: [`validate_agent_bundle`](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/server/bundles.py#L13-L75) The validator already treats uploaded bundles as untrusted in some ways. For example, it disables server-side environment expansion and can enforce a policy-handler allowlist: ```python spec = load( bundle_bytes, dest=Path(tmpdir) / "agent", expand_env=False, enforce_handler_allowlist=enforce_handler_allowlist, ) ``` However, the same validation does not reject `tools.<name>.callable` entries in an uploaded agent bundle. Python callable tools are an intended trusted/operator feature, but the upload path accepts them from tenant-provided bundles too. The docs describe server-side Python callable tools here: [`Python function tool` docs](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/docs/AGENT_YAML_SPEC.md#L229-L246) \ Later, the runner resolves and executes those callables: [`_resolve_spec_callable` imports the dotted path](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/runner/tool_dispatch.py#L444-L481) ```python mod = importlib.import_module(module_name) fn = getattr(mod, attr_name, None) ``` [`_execute_spec_callable_tool` calls the resolved function](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/runner/tool_dispatch.py#L484-L511) ```python result = await asyncio.to_thread(resolved, **args) ``` The high-level tool dispatcher falls back to this callable execution path: [`execute_tool` callable fallback](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/runner/tool_dispatch.py#L3958-L3965) ```python output = await _execute_spec_callable_tool(tool_name, args, agent_spec=agent_spec) ``` The problem is the trust boundary. Python callables are a trusted local developer feature, but uploaded agent bundles can be user-controlled in a hosted/multi-user server. The upload validator blocks some trusted-only policy behavior, but it does not block trusted-only tool callables. Suggested fix: when validating HTTP-uploaded bundles on a shared/multi-user server, reject server-side Python callable tools unless they are explicitly allowlisted by the operator. A conservative fix would reject `callable:` tool paths for tenant-uploaded bundles, while keeping trusted local/operator-authored configs working. ### Impact This is authenticated RCE against the Omnigent runner environment. A normal authenticated user who can upload or create a custom agent bundle can declare a server-side Python callable and have the runner import and execute it. Because the callable runs inside the runner process, the attacker-controlled code runs with the runner's permissions. In a hosted or multi-user deployment, this can expose runner-accessible files, environment variables, credentials, workspace data, internal services reachable from the runner, and runner availability. This is high impact because it crosses the boundary from "upload an agent config" to "execute local code on shared runner infrastructure" without requiring admin/operator access.

CVE-2026-62675 Affected Omnigent Versions

1 component(s)
Fixed Versions:
0.3.0
Product / Package Ecosystem Affected Versions Fixed Version
omnigent
PyPI
< 0.3.0
0.3.0

References

Frequently Asked Questions

What is CVE-2026-62675?
CVE-2026-62675 is a security vulnerability in Omnigent involving Uploaded Agent Bundle Allows Authenticated Runner RCE via Python Callable Tools under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which Omnigent versions are affected?
Affected versions include releases prior to 0.3.0 across affected packages: omnigent.
What version fixes CVE-2026-62675?
Upgrading to 0.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is omnigent affected?
Yes, omnigent is affected in releases prior to 0.3.0. Upgrade your dependency to 0.3.0 or later.
What is the CVSS score of CVE-2026-62675?
CVE-2026-62675 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-62675?
CVE-2026-62675 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check PyPI dependencies for CVE-2026-62675?
Run the dependency tree command: 'pip show omnigent'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-756x-9hf6-q4h4",
  "modified" : "2026-09-02T21:54:52Z",
  "published" : "2026-09-02T21:54:52Z",
  "aliases" : [ "CVE-2026-62675" ],
  "summary" : "Omnigent: Uploaded Agent Bundle Allows Authenticated Runner RCE via Python Callable Tools",
  "details" : "### Summary\n\nAn 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.\n\nWhen the tool is invoked, the runner imports and executes that Python callable. A crafted bundle can point the tool at `subprocess.check_output`, which lets the attacker run a local command on the runner machine.\n\nThis 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.\n\n### Details\n\nThe 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:\n\n[`Create custom agent` builds and uploads a bundle](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/ap-web/src/shell/NewChatDialog.tsx#L1265-L1277) \n\\\n[`createBundledSession` posts the bundle to `/v1/sessions`](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/ap-web/src/lib/sessionsApi.ts#L421-L460)\n\nA crafted bundle can also be submitted directly through the API/CLI when creating a session from agent YAML. The PoC below uses this direct bundle shape so the vulnerable trust boundary is easy to reproduce.\n\nOn the server, uploaded bundles are validated here:\n[`validate_agent_bundle`](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/server/bundles.py#L13-L75)\n\nThe validator already treats uploaded bundles as untrusted in some ways. For example, it disables server-side environment expansion and can enforce a policy-handler allowlist:\n```python\nspec = load(\n    bundle_bytes,\n    dest=Path(tmpdir) / \"agent\",\n    expand_env=False,\n    enforce_handler_allowlist=enforce_handler_allowlist,\n)\n```\nHowever, the same validation does not reject `tools.<name>.callable` entries in an uploaded agent bundle. Python callable tools are an intended trusted/operator feature, but the upload path accepts them from tenant-provided bundles too.\n\nThe docs describe server-side Python callable tools here: [`Python function tool` docs](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/docs/AGENT_YAML_SPEC.md#L229-L246)\n\\\nLater, the runner resolves and executes those callables: [`_resolve_spec_callable` imports the dotted path](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/runner/tool_dispatch.py#L444-L481)\n```python\nmod = importlib.import_module(module_name)\nfn = getattr(mod, attr_name, None)\n```\n[`_execute_spec_callable_tool` calls the resolved function](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/runner/tool_dispatch.py#L484-L511)\n```python\nresult = await asyncio.to_thread(resolved, **args)\n```\nThe high-level tool dispatcher falls back to this callable execution path: [`execute_tool` callable fallback](https://github.com/omnigent-ai/omnigent/blob/23d42d9a7d46a3b6a0b40d5bf4125b91193bf831/omnigent/runner/tool_dispatch.py#L3958-L3965)\n```python\noutput = await _execute_spec_callable_tool(tool_name, args, agent_spec=agent_spec)\n```\n\nThe problem is the trust boundary. Python callables are a trusted local developer feature, but uploaded agent bundles can be user-controlled in a hosted/multi-user server. The upload validator blocks some trusted-only policy behavior, but it does not block trusted-only tool callables.\n\nSuggested fix: when validating HTTP-uploaded bundles on a shared/multi-user server, reject server-side Python callable tools unless they are explicitly allowlisted by the operator. A conservative fix would reject `callable:` tool paths for tenant-uploaded bundles, while keeping trusted local/operator-authored configs working.\n\n### Impact\n\nThis is authenticated RCE against the Omnigent runner environment. A normal authenticated user who can upload or create a custom agent bundle can declare a server-side Python callable and have the runner import and execute it.\n\nBecause the callable runs inside the runner process, the attacker-controlled code runs with the runner's permissions. In a hosted or multi-user deployment, this can expose runner-accessible files, environment variables, credentials, workspace data, internal services reachable from the runner, and runner availability.\n\nThis is high impact because it crosses the boundary from \"upload an agent config\" to \"execute local code on shared runner infrastructure\" without requiring admin/operator access.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "omnigent"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/omnigent-ai/omnigent/security/advisories/GHSA-756x-9hf6-q4h4"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-62675"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnigent-ai/omnigent/pull/1430"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnigent-ai/omnigent/commit/1f3f398f41cbf97b905133c21e848621c21da6e0"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/omnigent-ai/omnigent"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/omnigent-ai/omnigent/releases/tag/v0.3.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-94" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-02T21:54:52Z",
    "nvd_published_at" : "2026-08-21T18:16:49Z"
  }
}