OSV-2025-1097 Security exception in org.htmlunit.cyberneko.HTMLTagBalancer.reopenFormattingElements
Not scored
Published
Check this codebase for OSV-2025-1097 and fix it if it is affected.
What it is: OSV-2025-1097 is a vulnerability in htmlunit, published on 10 Oct 2026.
Exploitation: There is no known exploitation of OSV-2025-1097 in the wild and no public exploit code.
Affected packages and fixed versions:
- htmlunit (OSS-Fuzz): 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/OSV-2025-1097/ (Markdown: https://insights.sbomify.com/OSV-2025-1097/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is OSV-2025-1097?
OSV-2025-1097 is a vulnerability in htmlunit, published on 10 Oct 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=571721880
Crash type: Security exception
Crash state:
org.htmlunit.cyberneko.HTMLTagBalancer.reopenFormattingElements
org.htmlunit.cyberneko.HTMLTagBalancer.startElement
org.htmlunit.cyberneko.HTMLTagBalancer.forceStartElement
Which versions are affected by OSV-2025-1097?
1 open source package ship an affected version, including htmlunit.
| Package | Affected | Fixed in |
|---|---|---|
htmlunit OSS-Fuzz | All versions | None |
How do I fix OSV-2025-1097?
No fix has been published for OSV-2025-1097 yet. Limit exposure of the affected software until one is available.
Is OSV-2025-1097 being exploited?
There is no known exploitation of OSV-2025-1097 in the wild and no public exploit code.