CVE-2026-32732 — @leanprover/unicode-input…
Fix: leanprover/vscode-lean4#735CVE-2026-32732 is a CWE-80 vulnerability in @leanprover/unicode-input-component. A fix is available for @leanprover/unicode-input-component — see the affected versions and patch details below.
XSS in @leanprover/unicode-input-component
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32732.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@leanprover/unicode-input-componentnpmDescription
Impact
Projects that use @leanprover/unicode-input-component are vulnerable to an XSS exploit in 0.1.9 of the package and lower. The component re-inserted text in the input element back into the input element as unescaped HTML.
Patches
The issue has been resolved in 0.2.0.
Workarounds
Replace the unicode input component with a basic HTML text field.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @leanprover/unicode-input-component | all versions | 0.2.0npm install @leanprover/unicode-input-component@0.2.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @leanprover/unicode-input-component, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @leanprover/unicode-input-component to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32732 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-32732 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-32732. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-32732 in your dependencies?
O3 Security finds CVE-2026-32732 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.