# CVE-2026-73614: Network-AI ClaudeHookBridge Deny Pattern Bypass via Truncation

> Attackers bypass deny patterns by placing malicious commands beyond the 500-character truncation limit, enabling arbitrary code execution in Claude Hook Bridge.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-64vj-7c55-24w2, GHSA-743h-jr5x-mpcr

## What is CVE-2026-73614?

CVE-2026-73614 is a high-severity vulnerability in Jovancoding Network-AI, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Network-AI ClaudeHookBridge before 5.15.1 truncates the target string to 500 characters before evaluating denyPatterns, while Claude Code executes the full untruncated command. Attackers can position dangerous content past byte 500 in a Bash command field to bypass the operator's hard-deny list and execute arbitrary commands.

Weakness: CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2026-73614?


## How do I fix CVE-2026-73614?

No fix has been published for CVE-2026-73614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73614 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73614 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73614 and fix it if it is affected.

What it is: CVE-2026-73614 is a high-severity vulnerability in Jovancoding Network-AI, published on 13 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73614 exists.

Affected product: Jovancoding Network-AI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73614/ (Markdown: https://insights.sbomify.com/CVE-2026-73614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73614
- OSV: https://osv.dev/vulnerability/CVE-2026-73614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73614/
Summaries are generated and may contain mistakes; the official description above is the record.