vciy

CVE-2011-0026

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Integer signedness error in the SQLConnectW function in an ODBC API (odbc32.dll) in Microsoft Data Access Components (MDAC) 2.8 SP1 and SP2, and…

CVE-2011-00263 of 4 sources documented this
36

rank 36 = 9 + 23 + 0 + 4 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.34399  ·  without this subject the record ranks 27

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.3, from NVD  ·  without this subject the record ranks 13

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 36

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 32

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 36

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.72Mover the next 30 days, if this record is yours
Movement-$47,200on 2024-09-04, the last material move, 1 year, 9 months before this reading
Basisassumeda published average, not your estate

$1.72M = $4.99M incident cost x 1 exposure x 0.34399 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.34399EPSSNOT IN KEVas of 2026-09-20
Severity9.3 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementthreshold crossedreceipt
FALLING10Fallen from 0.6716 to 0.34399 across 17 observations. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Check a version against this record

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no authenticationreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v2.0 · NVD's vectorreceipt
Weakness classCWE-189receipt
Published consequencesMITRE publishes no common consequences for this weakness.[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 15 Jun 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD9.3 CRITICALreceipt
Exploit probability0.34399 · top 2% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes17 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Named in the CPE rangesMicrosoft data access components; Microsoft windows data access componentsreceipt
Published rangesmicrosoft data access components 2.8; microsoft windows data access components 6.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Integer signedness error in the SQLConnectW function in an ODBC API (odbc32.dll) in Microsoft Data Access Components (MDAC) 2.8 SP1 and SP2, and Windows Data Access Components (WDAC) 6.0, allows remote attackers to execute arbitrary code via a long string in the Data Source Name (DSN) and a crafted szDSN argument, which bypasses a signed comparison and leads to a buffer overflow, aka "DSN Overflow Vulnerability." receipt

NVD's analysis a second authority

severity
9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
weakness
CWE-189
affected versions
microsoft data access components 2.8; microsoft windows data access components 6.0

check it yourself vupen.com securityfocus.com docs.microsoft.com osvdb.org securitytracker.com oval.cisecurity.org +4 morereceipt

Dated events

2023-03-26EPSS moved 0.62 to 0.692026-06-15EPSS moved 0.64 to 0.34

Movement the material steps

4 Feb 20220.6716
7 Mar 20230.62426 · scoring model v2023.03.01
20 May 20230.88183
12 Jul 20230.90192 · crossed 0.90
4 Sep 20240.89247 · crossed 0.90
17 Mar 20250.64601 · scoring model v2025.03.14
15 Jun 20260.34399 · crossed 0.50 · scoring model v2026.06.15
Show all 17 observations
4 Feb 20220.6716
7 Mar 20230.62426
26 Mar 20230.68940
20 May 20230.88183
12 Jul 20230.90192
4 Sep 20240.89247
17 Dec 20240.80048
17 Mar 20250.64601
19 Mar 20250.60973
29 Mar 20250.61212
30 Mar 20250.60973
1 Oct 20250.64297
27 Oct 20250.60973
28 Oct 20250.64297
27 Dec 20250.60973
28 Dec 20250.64297
15 Jun 20260.34399

17 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.34399Published2011-01-12Index as of2026-06-15

The record had been public for 15 years, 5 months when this index was last written.

Published 2011-01-12 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2011-0026.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.