CVE-2026-32714 | SciTokens up to 1.9.5 str.format sql injection (GHSA-rh5m-2482-966c)

VDB-354307 · CVE-2026-32714 · GHSA-RH5M-2482-966C SCITOKENS UP TO 1.9.5 STR.FORMAT SQL INJECTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 8.4 $0-$5k 0.99+ Summaryinfo A vulnerability identified as critical has been detected in SciTokens up to 1.9.5. This affects the function str.format. This manipulation causes sql injection. This vulnerability is tracked as CVE-2026-32714. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component. Detailsinfo A vulnerability has been found in SciTokens up to 1.9.5 and classified as critical. Affected by this vulnerability is the function str.format. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is: 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. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-32714 since 03/13/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK. Upgrading to version 1.9.6 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 3dba108853f2f4a6c0f2325c03779bf083c41cf2 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Name SciTokens Version 1.9.0 1.9.1 1.9.2 1.9.3 1.9.4 1.9.5 License open-source Website Product: https://github.com/scitokens/scitokens/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 8.5 VulDB Meta Temp Score: 8.4 VulDB Base Score: 7.3 VulDB Temp Score: 7.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 9.8 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Sql injection CWE: CWE-89 / CWE-74 / CWE-707 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: SciTokens 1.9.6 Patch: 3dba108853f2f4a6c0f2325c03779bf083c41cf2 Timelineinfo 03/13/2026 CVE reserved 03/31/2026 +17 days Advisory disclosed 03/31/2026 +0 days VulDB entry created 03/31/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-rh5m-2482-966c Status: Confirmed CVE: CVE-2026-32714 (🔒) GCVE (CVE): GCVE-0-2026-32714 GCVE (VulDB): GCVE-100-354307 Entryinfo Created: 03/31/2026 08:12 Changes: 03/31/2026 08:12 (67) Complete: 🔍 Cache ID: 99:08E:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸