HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 104774 owasp coraza waf jsdecode off by one in octal
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 5.8CVE-2026-104774GHSA-PC5Q-QFXP-GGQV

OWASP Coraza WAF: jsDecode Off-by-One in Octal Escape Handling Enables WAF BypassCVE-2026-104774

Answer in brief

CVE-2026-104774 records a Medium severity (CVSS 5.8) vulnerability in OWASP Coraza WAF: jsDecode Off-by-One in Octal Escape Handling Enables WAF Bypass. The current sources do not mark it as known exploited. The current feed maps corazawaf/coraza (generic), github.com/corazawaf/coraza/v3 (go), github.com/corazawaf/coraza/v3 (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 12, 2026Updated Oct 12, 2026Source checked Oct 12, 2026First seen by HOL Oct 8, 2026Material review Oct 12, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.8
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps corazawaf/coraza (generic), github.com/corazawaf/coraza/v3 (go), github.com/corazawaf/coraza/v3 (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
corazawaf/corazageneric>=3.0.0 <3.8.03.8.0
github.com/corazawaf/coraza/v3go>=3.0.0,<3.8.03.8.0
github.com/corazawaf/coraza/v3go>=3.0.0 <3.8.03.8.0

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for corazawaf/coraza, github.com/corazawaf/coraza/v3, github.com/corazawaf/coraza/v3.
  2. 2Review the reported fix. Update corazawaf/coraza to 3.8.0; github.com/corazawaf/coraza/v3 to 3.8.0; github.com/corazawaf/coraza/v3 to 3.8.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Oct 12, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 12, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Oct 8, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source description

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. From 3.0.0 until 3.8.0, the t:jsDecode transformation in internal/transformations/js_decode.go:64-70 includes the backslash in the octal buffer, causing ParseInt to fail and return a null byte. The flaw is triggered when a rule relies on t:jsDecode and the request contains JavaScript octal escape sequences. An unauthenticated attacker can encode attack syntax with JavaScript octal escapes so the backend decodes the intended bytes while Coraza rules using t:jsDecode inspect corrupted null-byte output. The mismatch can bypass WAF rules and expose the protected application to attacks such as cross-site scripting or SQL injection. This issue is fixed in version 3.8.0.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Super Productivity: SuperSync E2EE setup uploads and stores all user operations in plaintext before password is setAlso CWE-693
  • Nginx UI: MCP nginx_config_add skips config directive validation → authenticated nginx directive injection (RCE on the official image)Also CWE-693
  • Nginx UI: MCP configuration tools bypass restricted directive validation and allow secondary authenticated users to execute NJS in Nginx worker contextAlso CWE-693
  • easy-pdf-merge 0.1.0 through 0.2.6 OS Command Injection via merge functionSame generic ecosystem
  • cbor-sync through 1.0.4 Memory Exhaustion via Unchecked CBOR Array LengthsSame generic ecosystem
  • Servor 1.0.0 through 4.0.2 Unauthenticated Path Traversal via URL-Encoded Dot SegmentsSame generic ecosystem

Record context

Vulnerability class
SQL Injection
EPSS
Not reported
CWE IDs
CWE-172, CWE-193, CWE-693
Source
CVE List V5
Source checked
Oct 12, 2026
References
5 linked sources
Open source record