ACVE-2025-0006

The configuration

Configuration label

claude-code <1.0.39 + project hooks

Affected entries

• AgentHarness: claude-code — SEMVER (introduced 0; fixed 1.0.39)

Matcher

• all
  • harness.id eq "claude-code"
  • harness.version semverRange "<1.0.39"
  • some hooks
    • scope eq "project"

Why it is exploitable

What the vulnerability is

Claude Code project-scoped hooks can cause repository-controlled content to influence configuration or command execution. The referenced claim is associated with Claude Code releases before the fixed boundary recorded by this advisory. The risk is specific to hooks loaded from a project rather than only from a user-controlled global configuration.

Which configuration is exposed

The matcher exposes Claude Code when harness.id is claude-code, harness.version is below 1.0.39, and at least one entry in hooks has scope equal to project. It deliberately does not require a particular hook event, command, script path, or permission mode. A project hook is therefore the harness/tool combination that makes the rule match; the lockfile signal does not prove that the hook is malicious or that it has run.

How ACVE detects it

ACVE reads harness.id, harness.version, and hooks[].scope. It cannot inspect the hook's command body, source provenance, script contents, or whether a user approved execution. The fixed boundary is represented as 1.0.39 (unverified — see Grounding needed), and the finding should be treated as a review signal for any project-scoped hook.

Fix

1. Upgrade Claude Code to 1.0.39 or later after confirming the release boundary.
2. Review every project-scoped hook, remove hooks that are not required, and require an explicit approval boundary before running repository-controlled commands.

Grounding needed

acve advisory ground must confirm the affected range and fixed Claude Code release for CVE-2025-59536, including whether 1.0.39 is the correct boundary.

References

See references for primary sources.

Underlying CVEs / aliases

• CVE-2025-59536

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

Upgrade Claude Code to the confirmed fixed release and review project hooks.

Validation

No validation entries recorded.

Grounding

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

References

ADVISORY

• https://nvd.nist.gov/vuln/detail/CVE-2025-59536

REPORT

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

FIX

• https://github.com/pickbitsai/acve/issues?q=CVE-2025-59536