CVE-2013-3900 — Microsoft WinVerifyTrust function Remote Code Execution

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 — msrc.microsoft.com (NIST National Vulnerability Database)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Jul 10, 2022 — passed 1558 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 Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809…).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. Apply the fixed version or the patch documented under Remediation.
4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
5. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
6. Search available logs for exploit probes matching the vulnerability class (cryptography), 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-347 · Improper Verification of Cryptographic Signature

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.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 44.65%

Detection

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

• Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
• Check TLS negotiations and unexpected certificates in the component’s traffic.
• Hunt retroactively in logs from before Jan 10, 2022 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · microsoft/windows 10 version 1809, microsoft/windows server 2019, microsoft/windows server 2019 (server core installatio
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• 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/windows 10 1507, microsoft/windows 10 1607, microsoft/windows 10 1809, microsoft/windows 10 1909, microsoft/wi
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 5.5
  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
• 2022
• Added to CISA KEV catalog
  Jan 9, 2022 · CISA
• 2013
• CVE published
  Dec 10, 2013 · 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

6 on the record

• docs.microsoft.com/en-us/security-updates/securitybulletins/2013/ms13-098
  Vendor Advisory, NIST National Vulnerability Database
• msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
  Patch, Vendor Advisory, vendor-advisory, NIST National Vulnerability Database
• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database
• github.com/advisories/GHSA-8cj2-jg77-qj2p
  GitHub Security Advisories
• nvd.nist.gov/vuln/detail/CVE-2013-3900
  GitHub Security Advisories
• blogs.technet.com/b/srd/archive/2013/12/10/ms13-098-update-to-enhance-the-security-of-a
  Broken Link, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
• Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
• Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
• Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d
• Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d
• Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d

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-2013-3900 is "Microsoft WinVerifyTrust function Remote Code Execution", rated Medium. It affects Windows 10 1507 (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 5.5 describes technical severity. EPSS 44.65% 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.