# CVE-2025-24369: Anubis has a bot protection bypass when a sophisticated attacker asks to pass a challenge of difficulty 0

> Attackers can bypass Anubis bot protection by requesting a zero-difficulty challenge, allowing unauthorized scraping.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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:** Yes
- **Published:** 27 Jan 2025
- **Updated:** 28 Jan 2025
- **Also known as:** GHSA-56w8-8ppj-2p4f, GO-2025-3424, openSUSE-SU-2025:15847-1

## What is CVE-2025-24369?

CVE-2025-24369 is a low-severity vulnerability in Xe x, published on 27 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Anubis is a tool that allows administrators to protect bots against AI scrapers through bot-checking heuristics and a proof-of-work challenge to discourage scraping from multiple IP addresses. Anubis allows attackers to bypass the bot protection by requesting a challenge, formulates any nonce (such as 42069), and then passes the challenge with difficulty zero. Commit e09d0226a628f04b1d80fd83bee777894a45cd02 fixes this behavior by not using a client-specified difficulty value.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

## Which versions are affected by CVE-2025-24369?

1 open source package ship an affected version, including github.com/Xe/x.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/Xe/x` | Go | All versions | None |
| `anubis` | openSUSE:Tumbleweed | All versions | 1.24.0-1.1 |

## How do I fix CVE-2025-24369?

Apply the vendor's patch.

## Is CVE-2025-24369 being exploited?

There is no known exploitation of CVE-2025-24369 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24369 and fix it if it is affected.

What it is: CVE-2025-24369 is a low-severity vulnerability in Xe x, published on 27 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24369 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/Xe/x (Go): affected all versions; no fix listed

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-2025-24369/ (Markdown: https://insights.sbomify.com/CVE-2025-24369/index.md)
```

## Sources

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

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