CVE-2010-3962 — Microsoft Internet Explorer Uninitialized Memory Corruption Vulnerability

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

• Documented patch — www.microsoft.com (NIST National Vulnerability Database)
• Documented patch — docs.microsoft.com (NIST National Vulnerability Database)

CISA required action CISA

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

US federal deadline: Oct 27, 2025 — passed 353 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Internet Explorer).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
4. Apply the fixed version or the patch documented under Remediation.
5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
6. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-416 · Use After Free

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 96.83%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
• Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
• Hunt retroactively in logs from before Oct 6, 2025 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• Fix documented
  Oct 13, 2026 · NIST National Vulnerability Database
• Affected products added · microsoft/internet explorer
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 8.1
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Added to CISA KEV (detected)
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Record created in this database
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• 2025
• Added to CISA KEV catalog
  Oct 5, 2025 · CISA
• 2010
• CVE published
  Nov 5, 2010 · microsoft

Source activity

Repeated readings are counted rather than listed.

• 2× References added · Oct 13, 2026 – Oct 13, 2026
• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

17 on the record

• blogs.technet.com/b/msrc/archive/2010/11/02/microsoft-releases-security-advisory-245851
  Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• www.vupen.com/english/advisories/2010/2880
  Broken Link, Vendor Advisory, vdb-entry, x_refsource_VUPEN, NIST National Vulnerability Database
• secunia.com/advisories/42091
  Broken Link, Vendor Advisory, third-party-advisory, x_refsource_SECUNIA, NIST National Vulnerability Database
• docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-090
  Patch, Vendor Advisory, vendor-advisory, x_refsource_MS, NIST National Vulnerability Database
• www.microsoft.com/technet/security/advisory/2458511.mspx
  Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database
• www.exploit-db.com/exploits/15421
  Third Party Advisory, VDB Entry, exploit, x_refsource_EXPLOIT-DB, NIST National Vulnerability Database
• exchange.xforce.ibmcloud.com/vulnerabilities/62962
  Third Party Advisory, VDB Entry, vdb-entry, x_refsource_XF, NIST National Vulnerability Database
• nvd.nist.gov/vuln/detail/CVE-2010-3962
  GitHub Security Advisories
• oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12279
  Tool Signature, vdb-entry, signature, x_refsource_OVAL, NIST National Vulnerability Database
• www.us-cert.gov/cas/techalerts/TA10-348A.html
  Third Party Advisory, US Government Resource, third-party-advisory, x_refsource_CERT, NIST National Vulnerability Database
• www.securitytracker.com/id
  Broken Link, Third Party Advisory, VDB Entry, vdb-entry, x_refsource_SECTRACK, NIST National Vulnerability Database
• github.com/advisories/GHSA-cmh7-cfjq-p92g
  GitHub Security Advisories
• www.kb.cert.org/vuls/id/899748
  Third Party Advisory, US Government Resource, third-party-advisory, x_refsource_CERT-VN, NIST National Vulnerability Database
• www.securityfocus.com/bid/44536
  Broken Link, Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID, NIST National Vulnerability Database
• www.exploit-db.com/exploits/15418
  Third Party Advisory, VDB Entry, exploit, x_refsource_EXPLOIT-DB, NIST National Vulnerability Database
• www.symantec.com/connect/blogs/new-ie-0-day-used-targeted-attacks
  Not Applicable, x_refsource_MISC, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• High CVE-2021-27085 Microsoft Internet Explorer Remote Code Execution Vulnerability KEV Mar 11, 2021
• High CVE-2021-26411 Microsoft Internet Explorer Memory Corruption Vulnerability KEV Mar 11, 2021
• Medium CVE-2020-0878 Microsoft Edge and Internet Explorer Memory Corruption Vulnerability KEV Sep 11, 2020
• High CVE-2020-1380 Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability KEV Aug 17, 2020
• High CVE-2020-0968 Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability KEV Apr 15, 2020
• High CVE-2020-0674 Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability KEV Feb 11, 2020

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2010-3962 is "Microsoft Internet Explorer Uninitialized Memory Corruption Vulnerability", rated High. It affects Internet Explorer (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.1 describes technical severity. EPSS 96.83% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.