Exploited CVEs / Microsoft / CVE-2013-3900

CVE-2013-3900

Microsoft WinVerifyTrust function Remote Code Execution. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-07-10 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Microsoft Security Update Guide (MSRC), linked below.

Risk summary

UnratedCISA KEV

CVSS base

Not scored

EPSS exploit probability

Unrated

Severity

2022-01-10

Added to KEV

2022-07-10 (past due)

CISA due date

Actively exploited Microsoft WinVerifyTrust function vulnerability. Added to the CISA KEV catalog 2022-01-10.

Senserva AI read on CVE-2013-3900 CISA required action Official fix for CVE-2013-3900 Admin questions

Senserva AI Opinion for CVE-2013-3900

Unusually, this WinVerifyTrust Authenticode flaw is still relevant on fully patched Windows: Microsoft shipped the stricter signature verification as an opt-in registry setting rather than a default, so attackers can still pad malicious code into signed executables that pass validation. Malware campaigns, including supply-chain attacks, have abused exactly this gap. Enabling the hardening is a configuration task, not a patch.

Do this: Set the EnableCertPaddingCheck registry values to enforce strict Authenticode verification across your Windows fleet.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2013-3900

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2013-3900, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2013-3900.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2013-3900: Microsoft WinVerifyTrust function Remote Code Execution
- Affected: Microsoft WinVerifyTrust function
- Severity: Unrated
- Added to CISA KEV: 2022-01-10; federal remediation due 2022-07-10
- Ransomware-linked: no
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

The fix ships from the vendor: Microsoft Security Update Guide (MSRC).

Do this now: Federal remediation deadline 2022-07-10; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2013-3900

Published: 2022-01-10
Last revised: 2022-01-10
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

2022-01-10 added to the CISA KEV catalog by CISA
2026-08-05 CVSS 0.0 to 5.5

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2022-07-10 (past due).

Official fix for CVE-2013-3900

The authoritative fix and affected-version list are published by the vendor. Find the WinVerifyTrust function advisory on Microsoft Security Update Guide (MSRC).

Microsoft Security Update Guide (MSRC)CISA KEV entry

Common questions about CVE-2013-3900

Is CVE-2013-3900 actively exploited?

Yes. CVE-2013-3900 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-01-10, which means exploitation in the wild has been confirmed, not predicted.

What is the CISA deadline and required action for CVE-2013-3900?

CISA set the federal (BOD 22-01) remediation due date at 2022-07-10, which has passed; treat any unremediated system as overdue.

What fixes CVE-2013-3900?

The authoritative fix is in the vendor advisory: see Microsoft Security Update Guide (MSRC) for the patched WinVerifyTrust function versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2013-3900?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2013-3900's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited Microsoft CVEs: CVE-2008-4250 CVE-2009-1537 CVE-2010-0249 CVE-2010-0806 CVE-2026-41091 CVE-2026-45498 CVE-2026-33825 CVE-2009-0238
All Microsoft exploited CVEs on one page: Microsoft vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog Microsoft MSRC FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.