dbcve.org
Scitokens LibraryApplication · Scitokens

CVE-2026-32714

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 1.9.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
SciTokens is a reference library for generating and using SciTokens. Prior to version 1.9.6, the KeyCache class in scitokens was vulnerable to SQL Injection because it used Python's str.format() to construct SQL queries with user-supplied data (such as issuer and key_id). This allowed an attacker to execute arbitrary SQL commands against the local SQLite database. This issue has been patched in version 1.9.6.

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 KeyCache class in scitokens library uses Python's str.format() to construct SQL queries with user-supplied data (issuer and key_id). This allows SQL injection attacks where attackers can execute arbitrary SQL commands against the local SQLite database.

MitigationUpgrade to scitokens version 1.9.6 or later, which patches the SQL injection vulnerability by using parameterized queries instead of string formatting.

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
Scitokens LibraryApplication
Affected:< 1.9.6

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. Check installed scitokens library version
    Run 'pip show scitokens' or 'pip list | grep scitokens' to display the installed version
    Affected if The installed version is lower than 1.9.6
  2. Confirm KeyCache class usage in your code
    Search your codebase for imports of KeyCache from scitokens (e.g., 'from scitokens._utils import KeyCache' or similar patterns) and any instantiation of this class
    Affected if Your application directly uses the KeyCache class to manage token caching
  3. Identify SQL query construction patterns
    Search the scitokens library source for uses of str.format() combined with SQL SELECT/INSERT/UPDATE statements, particularly in files related to caching or database operations
    Affected if The library code uses str.format() to build SQL queries rather than parameterized queries
  4. Check for user-supplied issuer or key_id handling
    Audit your application code to determine if external or user-controlled values are passed as the 'issuer' or 'key_id' parameters to scitokens functions that interact with KeyCache
    Affected if Your application passes unvalidated or externally-sourced issuer/key_id values to scitokens cache operations
  5. Verify SQLite database file exists and is accessible
    Locate the SQLite database file used by scitokens for caching (typically in a local cache directory) and confirm it is present
    Affected if A local SQLite database is being used by the scitokens KeyCache for storing cached tokens

You are affected if you are running scitokens version below 1.9.6 AND your application passes user-supplied issuer or key_id values to the KeyCache class, which then uses str.format() to construct SQL queries against a local SQLite database.

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 1.9.6 or later
Fixed in 1.9.6
Vendor patch github.com →
Interim mitigation

Upgrade to scitokens version 1.9.6 or later, which patches the SQL injection vulnerability by using parameterized queries instead of string formatting.

Recommended fix High confidence

1.9.6

  1. 1. Identify the current scitokens library version in your environment (e.g., pip show scitokens or your package manager's equivalent).
  2. 2. Upgrade the scitokens library to version 1.9.6 or later (e.g., pip install scitokens>=1.9.6).
  3. 3. Verify the upgrade was successful by checking the installed version.
  4. 4. Test your application to ensure the upgrade does not break existing functionality.

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

Fix this in Scitokens Library Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32714 — 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-32714 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