dbcve.org
Athena OdbcApplication · Amazon

CVE-2026-35561

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-03
Fix available
A fix is available. Upgrade to 2.1.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Insufficient authentication security controls in the browser-based authentication components in Amazon Athena ODBC driver before 2.1.0.0 might allow a threat actor to intercept or hijack authentication sessions due to insufficient protections in the browser-based authentication flows. To remediate this issue, users should upgrade to version 2.1.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Amazon Athena ODBC driver before version 2.1.0.0 contains insufficient authentication security controls in its browser-based authentication components. This vulnerability allows threat actors to intercept or hijack authentication sessions due to inadequate protections in the browser-based authentication flows used to authenticate to Amazon Athena.

MitigationUpgrade the Amazon Athena ODBC driver to version 2.1.0.0 or later to remediate the insufficient authentication security controls in the browser-based authentication flows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Athena OdbcApplication
Affected:< 2.1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the installed Amazon Athena ODBC driver version
    On Windows, open ODBC Data Source Administrator (odbcad32.exe), go to the Drivers tab, and find the Athena ODBC Driver entry to view its version. On Linux/macOS, check the driver installation directory or use package management tools (rpm -qa | grep -i athena or dpkg -l | grep -i athena) to identify the installed driver package and version.
    Affected if The reported version is lower than 2.1.0.0 (for example, 2.0.x, 1.x, or any version number below 2.1.0.0)
  2. Confirm browser-based authentication is configured
    Inspect the DSN (Data Source Name) configuration or connection string used for Athena connections. Look for authentication parameters such as AuthType=Browser, AuthenticationMethod=Browser, or similar settings that indicate the driver is configured to use AWS console/browser-based authentication rather than IAM credentials or IAM Role-based authentication.
    Affected if The driver is configured to use browser-based authentication (interactive AWS console login through the browser) as the authentication method
  3. Verify the authentication flow is operational
    Test establishing a connection to Athena using the ODBC driver. During the connection attempt, observe whether a browser window or embedded browser control opens to prompt for AWS credentials or role assumption, which indicates the vulnerable authentication flow is active.
    Affected if The connection attempt triggers a browser-based authentication prompt, confirming the affected authentication mechanism is in use

You are affected if the installed Amazon Athena ODBC driver version is below 2.1.0.0 AND the driver is configured to use browser-based authentication for AWS credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.0.0 or later
Fixed in 2.1.0.0
Vendor patch downloads.athena.us-east-1.amazonaws.com →
Interim mitigation

Upgrade the Amazon Athena ODBC driver to version 2.1.0.0 or later to remediate the insufficient authentication security controls in the browser-based authentication flows.

Recommended fix High confidence

2.1.0.0

  1. Download the Amazon Athena ODBC driver version 2.1.0.0 from the official AWS download location
  2. Uninstall the current vulnerable version of Athena ODBC driver
  3. Install the downloaded AmazonAthenaODBC-2.1.0.0.rpm package
  4. Verify the installed version is 2.1.0.0 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Athena Odbc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35561 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35561 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data