Incorrect Authorization Affecting swift package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-SWIFT-18533411
- published5 Aug 2026
- disclosed5 Aug 2026
Introduced: 5 Aug 2026
NewCVE-2026-71191 (opens in a new tab)How to fix?
There is no fixed version for Echo:latest swift.
NVD Description
Note: Versions mentioned in the description apply only to the upstream swift package and not the swift package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
In OpenStack Swift through 2.38.0, S3API middleware does not enforce that semantic x-amz-* headers are covered by the SigV4 signature on presigned URL requests. An attacker who obtains a presigned PUT URL can inject an unsigned X-Amz-Copy-Source header, causing Swift to perform a server-side copy from an arbitrary source object using the signer's authorization context. The attacker can read any object the signer has access to, provided the target project_id, container name, and object name are known. This affects all deployments using the default s3_acl=false configuration.