CVE-2026-16207

Published

19 July 2026

Modified

20 July 2026

CVSS Score v4 6.3

Click a component to see what it means

Raw vector

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS Score 0.0040 33th percentile

Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-16207 is a medium-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2026-45418

Vulnerability Data

A vulnerability was detected in django-tastypie up to 0.15.1. Impacted is the function ApiKeyAuthentication of the file tastypie/authentication.py. The manipulation results in use of get request method with sensitive query strings. The attack can be launched remotely. This attack is…

characterized by high complexity. The exploitability is considered difficult. The project was informed of the problem early through an issue report but has not responded yet.

CWE(s): CWE-598

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1552 Unsecured Credentials Credential Access

Adversaries may search compromised systems to find and obtain insecurely stored credentials.

attack.mitre.org →

Why these techniques?

Vulnerability exposes API keys in GET query strings, enabling capture of unsecured credentials via logs or network interception.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-26196Shared CWE-598

CVE-2025-13219Shared CWE-598

CVE-2026-44883Shared CWE-598

CVE-2025-0730Shared CWE-598

CVE-2026-62386Shared CWE-598

CVE-2026-10078Shared CWE-598

CVE-2026-15322Shared CWE-598

CVE-2026-26721Shared CWE-598

CVE-2026-25118Shared CWE-598

CVE-2025-41772Shared CWE-598

Affected Assets

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

Detect

Catch it (NIST detect / respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

V3.4.5
V14.2.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SC-9 Transmission Confidentiality

addresses: CWE-598

Protects sensitive data placed in query strings from interception in transit when confidentiality controls like HTTPS are enforced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly prevent embedding sensitive data in query strings as part of input-handling and data-flow design.

PR.DS-02 partial match

prevents

HTTPS encryption protects query strings in transit but does not address the root design flaw of placing sensitive data in URLs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match

detects

Security testing can detect sensitive data leakage via query strings.

A.8.12 Data leakage prevention partial match

mitigates

DLP solutions can detect and block sensitive data in URLs.

A.8.20 Networks security partial match

degrades

Network security controls can enforce HTTPS and block sensitive data in URLs.

A.8.26 Application security requirements partial match

prevents

Application security requirements should mandate avoiding sensitive data in query strings.