No exploitation reportedFix available

CVE-2017-16613

Q: Is CVE-2017-16613 actively exploited?

Active exploitation of CVE-2017-16613 has not been confirmed. Its EPSS score was 8.4% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2017-16613?

CVE-2017-16613 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

No exploitation reported by the sources we read.

Published2017-11-21
Fixed in1.3.0
WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

An issue was discovered in middleware.py in OpenStack Swauth through 1.2.0 when used with OpenStack Swift through 2.15.1. The Swift object store and proxy server are saving (unhashed) tokens retrieved from the Swauth middleware authentication mechanism to a log file as part of a GET URI. This allows attackers to bypass authentication by inserting a token into an X-Auth-Token header of a new request. NOTE: github.com/openstack/swauth URLs do not mean that Swauth is maintained by an official OpenStack project team.

Timeline

dates in UTC

2017-11-2113:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-16613?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-16613?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD

swauth

Branch	Affected	Fixed in	Source
1.3	< 1.3.0	1.3.0	OSV

Debian debian linux

Branch	Affected	Fixed in	Source
9.0	= 9.0	no fix published	NVD

Openstack swauth

Branch	Affected	Fixed in	Source
1.2	≤ 1.2.0	no fix published	NVD

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Update swauth to 1.3.0

Advisories and patches

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.09.8read 2026-10-23
NVDCVSS 2.07.5read 2026-10-23
NVDweakness (CWE)CWE-287read 2026-10-23
FIRST EPSSEPSS score8.4 %2026-10-23
OSVaffected packages—

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2017-11-21
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-16613?

Is CVE-2017-16613 actively exploited?

Active exploitation of CVE-2017-16613 has not been confirmed. Its EPSS score was 8.4% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-16613?

CVE-2017-16613 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running swauth? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database