dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-62314

MEDIUM · 5.8 CVSS v3.1 Published 2026-07-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
67/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Anubis is a Web AI Firewall Utility that challenges users' connections in order to protect upstream resources from scraper bots. From 1.22.0 until 1.26.0-pre1, lib/policy/checker.go PathChecker.Check() trusted the client-controlled X-Original-URI header before matching r.URL.Path, allowing an HTTP client to match default data/common/keep-internet-working.yaml ALLOW rules such as ^/\.well-known/.*$ and bypass the Anubis challenge. This issue is fixed in version 1.26.0-pre1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Anubis Web AI Firewall versions 1.22.0 through 1.26.0-pre1, the PathChecker.Check() function in lib/policy/checker.go incorrectly trusted the client-supplied X-Original-URI header for path matching instead of using the server-controlled r.URL.Path. This allowed attackers to send malicious X-Original-URI values matching ALLOW rules like ^/\.well-known/.*$ to bypass the challenge mechanism.

MitigationUpgrade to Anubis version 1.26.0-pre1 or later. As a defense-in-depth measure, ensure policy matching uses only server-controlled path variables (r.URL.Path) rather than client-supplied headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Anubis Web AI Firewall version
    Run 'anubisctl version' or inspect the binary/version file to determine the installed version number
    Affected if The installed version is 1.22.0, 1.23.x, 1.24.x, 1.25.x, or 1.26.0-pre1 (any version from 1.22.0 through 1.26.0-pre1)
  2. Identify PathChecker policy rules
    Examine the Anubis policy configuration files (typically in /etc/anubis/policy/ or the configured policy directory) and search for PathChecker definitions in lib/policy/checker.go or equivalent policy files
    Affected if PathChecker is configured with ALLOW rules that use regex patterns (such as ^/\.well-known/.*$) for path matching
  3. Verify X-Original-URI header processing
    Inspect the Anubis configuration or HTTP request logs to determine if the X-Original-URI header is being read and passed to PathChecker.Check()
    Affected if X-Original-URI header handling is enabled and PathChecker uses it for path validation instead of r.URL.Path alone
  4. Test for bypass vulnerability
    Send a request with X-Original-URI: /.well-known/anything to an endpoint that should be blocked, and observe if the request bypasses the challenge mechanism due to the header being matched against ALLOW rules
    Affected if Requests with malicious X-Original-URI values successfully bypass ALLOW rules that should block them

You are affected if Anubis Web AI Firewall version is between 1.22.0 and 1.26.0-pre1, PathChecker is using ALLOW rules with regex patterns, and X-Original-URI header processing is enabled, allowing client-supplied headers to bypass path-based access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Anubis version 1.26.0-pre1 or later. As a defense-in-depth measure, ensure policy matching uses only server-controlled path variables (r.URL.Path) rather than client-supplied headers.

Recommended fix High confidence

1.26.0-pre1

  1. 1. Identify the current version of Anubis being used by checking the binary or configuration
  2. 2. If the version is between 1.22.0 and 1.26.0-pre1 (inclusive), upgrade to version 1.26.0-pre1 or later
  3. 3. Verify the upgrade was successful by checking the new version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-62314 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data