ACVE-2026-0008

The configuration

Configuration label

gemini-cli + permissionMode=bypassPermissions

Affected entries

• AgentHarness: gemini-cli — SEMVER (introduced 0)

Matcher

• all
  • harness.id eq "gemini-cli"
  • permissionMode eq "bypassPermissions"

Why it is exploitable

What the vulnerability is

Gemini CLI's yolo mode disables the normal approval boundary for tool use. This ACVE-native advisory describes a dangerous configuration combination rather than a newly assigned CVE: the harness is configured to bypass permissions, so tool requests can be accepted without the ordinary approval step.

Which configuration is exposed

The matcher requires harness.id gemini-cli and permissionMode equal to bypassPermissions. Those are the complete conditions encoded by this rule. It does not require a particular tool, repository, model, prompt, or MCP server, and it does not claim that every accepted tool is malicious; the exposure is the disabled approval boundary itself.

How ACVE detects it

ACVE reads harness.id and permissionMode from the lockfile. It cannot see which command or tool is about to run, whether the user intended yolo mode, or whether a separate operating-system control limits the process. The finding is a configuration warning that remains valid even when no tool has yet been invoked.

Fix

1. Disable yolo mode by changing the permission mode from bypassPermissions to default or another mode that requires approval.
2. Rebuild the lockfile and verify that the effective permission mode no longer bypasses approvals.

Because this is a policy weakness, the remediation is a settings change and a verification of the effective mode rather than a package upgrade.

The lockfile can show the effective mode, but it cannot show whether a person intended to accept the added risk for one particular task.

References

See references for primary sources.

Underlying CVEs / aliases

No CVE assigned. ACVE-native configuration weakness; no CVE assigned.

Detect

npx @pickbitsai/acve audit

For CI, emit SARIF with npx @pickbitsai/acve audit --format sarif --out acve.sarif --apply and upload it with GitHub code scanning.

Fix

Disable yolo mode and require approval for tools.

Validation

No validation entries recorded.

Grounding

• OSV: not found; checked-at 2026-09-20T02:43:29Z
• NVD: not found; checked-at 2026-09-20T02:43:29Z
• KEV: not listed in KEV; checked-at 2026-09-20T02:43:29Z

References

ADVISORY

• https://example.com/research/acve

REPORT

• https://example.com/research/acve