Summary
Anubis: Policy bypass via client controlled X-Original-URI header
Any HTTP client can bypass Anubis bot protection on the default configuration by adding a single request header. No challenge needs to be solved.
Affected versions: v1.22.0 through v1.25.0 (introduced in commit d1d631a, PR #1015)
The root cause is in lib/policy/checker.go, PathChecker.Check():
func (pc *PathChecker) Check(r *http.Request) (bool, error) {
originalUrl := r.Header.Get("X-Original-URI")
if originalUrl != "" {
if pc.regexp.MatchString(originalUrl) {
return true, nil
}
}
if pc.regexp.MatchString(r.URL.Path) {
return true, nil
}
return false, nil
}
The header value comes directly from the client request. The middleware chain never strips it. In reverse proxy mode an attacker fully controls it.
The default policy imports data/common/keep-internet-working.yaml, which contains path-only ALLOW rules with no other conditions:
- name: well-known
path_regex: ^/\.well-known/.*$
action: ALLOW
When X-Original-URI matches one of those regexes, the rule fires as ALLOW and the request is forwarded upstream without any challenge or JWT check.
Proof of concept
Normal request, gets challenged:
curl -s https://anubis.techaro.lol/ | grep -o "<title>.*</title>"
Bypass, gets upstream content:
curl -s -H "X-Original-URI: /.well-known/x" https://anubis.techaro.lol/ | grep -o "<title>.*</title>"
The first command returns the Anubis challenge page title. The second returns the real site title directly, with no cookie set and no challenge issued. Verified live against anubis.techaro.lol.
Impact
CVE-2026-62314 has a CVSS score of 5.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.26.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The fix should probably be to strip the header from incoming client requests in the middleware chain before policy evaluation. In auth_request mode the header is set by the proxy after Anubis processes the middleware, so stripping it at ingress does not break that deployment mode.
Frequently Asked Questions
- What is CVE-2026-62314? CVE-2026-62314 is a medium-severity security vulnerability in github.com/TecharoHQ/anubis (go), affecting versions >= 1.22.0, < 1.26.0. It is fixed in 1.26.0.
- How severe is CVE-2026-62314? CVE-2026-62314 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/TecharoHQ/anubis are affected by CVE-2026-62314? github.com/TecharoHQ/anubis (go) versions >= 1.22.0, < 1.26.0 is affected.
- Is there a fix for CVE-2026-62314? Yes. CVE-2026-62314 is fixed in 1.26.0. Upgrade to this version or later.
- Is CVE-2026-62314 exploitable, and should I be worried? Whether CVE-2026-62314 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-62314 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-62314? Upgrade
github.com/TecharoHQ/anubisto 1.26.0 or later.