# CVE-2026-85485: HTML::FormHandler versions before 0.410002 for Perl render some error messages into HTML without escaping

> Attacker can inject JavaScript via unescaped error messages in specific HTML::FormHandler layouts, leading to cross-site scripting.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-85485, GHSA-m5h3-w9r6-p935, UBUNTU-CVE-2026-85485

## What is CVE-2026-85485?

CVE-2026-85485 is a medium-severity cross-site scripting vulnerability, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

HTML::FormHandler versions before 0.410002 for Perl render some error messages into HTML without escaping.

The Table form layout and the Bootstrap 2 and 3 wrappers splice each error string straight into the surrounding markup. Version 0.410000, the fix for CVE-2026-19872, escaped the equivalent values in the other layouts and wrappers, and 0.410002 extended that to these three.

Error messages that contain attacker-influenced content such as rejected field values could embed JavaScript in rendered pages.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-85485?


## How do I fix CVE-2026-85485?

Upgrade to a fixed version.

## Is CVE-2026-85485 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85485 and fix it if it is affected.

What it is: CVE-2026-85485 is a medium-severity cross-site scripting vulnerability, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-85485 in the wild and no public exploit code.

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

## Sources

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

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