CVE-2026-120212

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-121639 (ENISA EUVD) · GHSA-3xh6-x477-72h3 (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

Upgrade to Web-Simple 0.037 or later (from the CVE record's solution, CPAN Security Group) — apply it.

Web::Simple versions before 0.037 for Perl do not escape single quotes in HTML::Tags output.

HTML::Tags and XML::Tags escape a plain string value by replacing only &, ", < and > with entities. A value interpolated into a single-quoted attribute, as in , can therefore close the attribute and add new ones, such as an event handler. Double-quoted attributes are not affected.

An attacker who controls a value that an application interpolates into a single-quoted attribute can inject script into the generated page.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 10, 2026

Last Modified

November 12, 2026

Vendor Advisories for CVE-2026-120212(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libweb-simple-perl0.033-2, 0.035-1, 0.036-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libweb-simple-perl0.033-2, 0.035-1, 0.036-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libweb-simple-perl0.033-2, 0.035-1, 0.036-1
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 20:30 UTCEchelonGraph re-scored
  2. 2026-11-12 20:30 UTCGHSA enrichmentGHSA-3xh6-x477-72h3
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-11-10 19:00 UTCENISA EUVD ID recordedEUVD-2026-121639 · Source: ENISA EUVD
  6. 2026-11-10 18:38 UTCGHSA enrichmentGHSA-3xh6-x477-72h3
  7. 2026-11-10 18:27 UTCNVD update
  8. 2026-11-10 17:45 UTCEchelonGraph re-scored
  9. 2026-11-10 17:44 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-120212?
CVE-2026-120212 is a vulnerability whose severity is not yet rated; its CVE record was published on November 10, 2026. Web::Simple versions before 0.037 for Perl do not escape single quotes in HTML::Tags output. HTML::Tags and XML::Tags escape a plain string value by replacing only &, ", < and > with entities. A value interpolated into a single-quoted attribute, as in <a href='$value'>, can therefore close the…
When was the CVE record for CVE-2026-120212 published?
The CVE record for CVE-2026-120212 was published on November 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-120212 actively exploited?
CVE-2026-120212 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-120212?
The CVE record's solution for CVE-2026-120212, written by its CNA CPAN Security Group, names the fix: "Upgrade to Web-Simple 0.037 or later." The vendor advisories EchelonGraph has for CVE-2026-120212 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-120212

Explore →

Is Your Infrastructure Affected by CVE-2026-120212?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.