CVE-2025-46727VulnerabilityPublished 2 Jun 2025Updated 11 Oct 2026

SUSE · Important: pcs security update

Affects SUSESource GCVE Database

Not known to be exploited : upgrade SUSE to 3.0.0 soon.

Data as of 26 Oct 2026, 09:15 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.0

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade rack to 3.0.0.

Affected software

Product	Affected	Fixed in
RubyGemsrack`pkg:gem/rack`Other threats	Affected <3.0.0	Fixed in 3.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated packages for Red Hat Satellite 6.17 that fix this vulnerability. Users are advised to apply these updates promptly. Before applying the update, ensure all previously released errata relevant to the system have been applied. Detailed update instructions are available in Red Hat's official documentation. Patch status is confirmed by the vendor advisory indicating an official fix is available.

Description

Red Hat Satellite is a system management solution that allows organizations to configure and maintain their systems without the necessity to provide public Internet access to their servers or other client systems. It performs provisioning and configuration management of predefined standard operating environments. Security Fix(es): * rubygem-rack: Unbounded-Parameter DoS in Rack::QueryParser (CVE-2025-46727) Users of Red Hat Satellite are advised to upgrade to these updated packages, which fix these bugs.

Impact

Successful exploitation of this vulnerability could allow an attacker to cause a denial of service condition on Red Hat Satellite systems by exhausting resources through unbounded parameter parsing. There are no known exploits in the wild at this time. The impact is limited to service availability disruption.

Summary

CVE-2025-46727 is an unbounded-parameter denial-of-service vulnerability in the Rack::QueryParser component of rubygem-rack, which is used by Red Hat Satellite. This vulnerability can be triggered by specially crafted requests that cause excessive resource consumption, leading to denial of service. Red Hat Satellite 6.17 and its Capsule and related packages are affected. Red Hat has issued an important security advisory (RHSA-2025:7604) and released updated packages that fix this vulnerability.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jul 2026, 11:21 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats