Under specific conditions, a malicious webpage may trigger autofill population after two consecutive taps, potentially without clear or intentional user consent. This could result in disclosure of stored autofill data such as addresses, email, or phone number metadata.
CVE-2026-0102
LOWPre-NVD 3.13.1—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-02-17. a secondary CVSS source baseline 3.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.1
- EG Score
- 3.1(medium)
- EG Risk
- 18(Track)EG Risk 18/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity31% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 38%
- KEV
- Not listed
Published
February 17, 2026
Last Modified
June 17, 2026
References (1)
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 13:25 UTCEG score recompute
- 2026-07-27 13:25 UTCVendor advisory
- 2026-07-27 13:25 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-0102?
CVE-2026-0102 is a low vulnerability published on February 17, 2026. Under specific conditions, a malicious webpage may trigger autofill population after two consecutive taps, potentially without clear or intentional user consent. This could result in disclosure of stored autofill data such as addresses, email, or phone number metadata.
When was CVE-2026-0102 disclosed?
CVE-2026-0102 was first published in the National Vulnerability Database on February 17, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0102 actively exploited?
CVE-2026-0102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.4% of all scored CVEs.
What is the CVSS score of CVE-2026-0102?
CVE-2026-0102 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-0102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-0102
Is Your Infrastructure Affected by CVE-2026-0102?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.