sqlmap credential leak via cross-host redirect handling
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in 1.10.11.89
- Who is exposed
- Not reported
Summary
The sqlmap tool can leak credentials: an attacker who controls the scanned target or abuses an open redirect can capture a user's Cookie and Authorization headers by making sqlmap's redirect handling forward them to an attacker-controlled host. The attack can be launched remotely without logging in, but it requires a user action to trigger.
Written by a model
Original description
sqlmap before 1.10.11.89 contains a credential exposure vulnerability that allows attackers to capture user-supplied Cookie and Authorization headers by redirecting requests to another host. Attackers controlling the scanned target or abusing an open redirect can make RedirectHandler.http_error_302 forward session cookies or bearer tokens to an attacker-controlled host.
What to do
Upgrade to a fixed version: 1.10.11.89.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133305 (sqlmap before 1.10.11.89 Credential Leak via Cross-Host HTTP Redirects), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133305 (entry last updated 2026-11-19):
Affected:
- sqlmapproject sqlmap: fixed in 1.10.11.89
Fixed versions: 1.10.11.89.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133305 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133305 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sqlmapproject/sqlmap/commit/5db2e62884d91f3ed3b43ec55904737e4051e9d7
- https://github.com/sqlmapproject/sqlmap/issues/6185
- https://github.com/sqlmapproject/sqlmap/blob/1.10.11/lib/request/redirecthandler.py#L179-L183
- https://github.com/sqlmapproject/sqlmap
- https://www.vulncheck.com/advisories/sqlmap-before-1.10.11.89-credential-leak-via-cross-host-http-redirects
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133305
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133305"}.Affected versions
- sqlmapproject sqlmapfixed in 1.10.11.89
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 46 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Exploit code on GitHub
VulnSVNC/CVE-2026-133305
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133305 |
| Record | NVD · CVE-2026-133305 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · VulnSVNC/CVE-2026-133305 · Repository |
| Other links 5 | |
| Patch | GitHub · sqlmapproject/sqlmap · Commit 5db2e628 |
| Report | GitHub · sqlmapproject/sqlmap · Issue #6185 |
| Repository | GitHub · sqlmapproject/sqlmap · lib/request/redirecthandler.py · L179-L183 |
| Repository | GitHub · sqlmapproject/sqlmap · Repository |
| Link | vulncheck.com · advisories/sqlmap-before-1.10.11.89-credential-leak-via-cross-host-http-redirects |
Questions about CVE-2026-133305
Is CVE-2026-133305 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).
Source: cve.now feed data
Which versions are affected by CVE-2026-133305?
sqlmap: before 1.10.11.89.
Source: cve.now feed data
How do I fix CVE-2026-133305?
Upgrade to a fixed version: 1.10.11.89.
Source: cve.now feed data
Related
- CVE-2026-114516Etherpad: Pre-auth arbitrary file read
- CVE-2026-86094Dimension Session Hijack via Exposed Session Tokens in Diagnostic Logs
- CVE-2026-84322Dimension Session Hijack via Exposed Session Tokens in Management API
- CVE-2026-131246Information Disclosure through REST API External Prompts in Splunk SOAR
- CVE-2026-59988django-docutils unsafe Docutils defaults allow local file disclosure, SSRF, and stored XSS
- CVE-2026-61798netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages
No corrections so far. Something wrong on this page? Report an error.