How severe is CVE-2026-32732?

No CVSS score has been assigned to CVE-2026-32732 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-32732?

CVE-2026-32732 affects the following packages: @leanprover/unicode-input-component (npm). Ecosystems affected: npm.

How do I fix CVE-2026-32732?

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.

How do I detect CVE-2026-32732 in my npm dependencies?

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.

How do I mitigate CVE-2026-32732 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-32732 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-32732 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-32732?

CVE-2026-32732 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-32732?

CVE-2026-32732 is classified as CWE-80 (CWE-80). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-32732 published, and has it been updated?

CVE-2026-32732 was published on March 16, 2026 and was last updated on March 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-32732 — @leanprover/unicode-input…

Fix: leanprover/vscode-lean4#735

CVE-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

Published

Mar 16, 2026

Updated

Mar 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@leanprover/unicode-input-componentnpm

158downloads / week

Description

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@leanprover/unicode-input-component`	all versions	0.2.0`npm install @leanprover/unicode-input-component@0.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact Projects that use [@leanprover/unicode-input-component](https://www.npmjs.com/package/@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.

O3 Security · Impact-Aware SCA

Is CVE-2026-32732 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works