Allocation of Resources Without Limits or Throttling Affecting github.com/sigstore/fulcio/pkg/identity package, versions <1.8.3
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 applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMSIGSTOREFULCIOPKGIDENTITY-14220411
- published8 Dec 2025
- disclosed5 Dec 2025
- creditAndrii Deinega
Introduced: 5 Dec 2025
NewCVE-2025-66506 Â (opens in a new tab)How to fix?
Upgrade github.com/sigstore/fulcio/pkg/identity to version 1.8.3 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the extractIssuerURL function. An attacker can cause excessive memory allocation by submitting a malicious request containing an OIDC identity token payload with a large number of period characters.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
wspackage