CVE-2026-26961VulnerabilityPublished 7 May 2026

SUSE · Security update for rmt-server

Affects SUSESource GCVE Database

Mentioned vulnerabilities

Not known to be exploited · fixed in SUSE package updates : patch SUSE soon.

Data as of 27 Oct 2026, 00:07 UTC

Severity

High

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

Patch: Available – fixed in 2.27

Exploitation evidence

Disclosed: evidence found.
CVE published 7 May 2026
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 or the CVSS exploit maturity 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.

Description

This update for rmt-server fixes the following issues: Update to version 2.27. Security issues fixed: - CVE-2026-26961: rack: greedy multipart boundary parsing can lead to parser differentials and WAF bypass (bsc#1261398). - CVE-2026-26962: rack: improper unfolding of folded multipart headers can lead to downstream header injection and response splitting(bsc#1261471). - CVE-2026-34763: rack: unescaped regex interpolation of configured root path can lead to root directory disclosure (bsc#1261406). - CVE-2026-34785: rack: prefix matching logic can lead to the exposure of unintended files under the static root (bsc#1261417). - CVE-2026-34786: rack: URL-encoded path mismatch can lead to `header_rules` bypass (bsc#1261426). - CVE-2026-34826: rack: missing individual byte range limit checks when parsing HTTP `Range` headers can lead to excessive resource consumption and a denial of service (bsc#1261436). - CVE-2026-34829: rack: multipart parsing without `Content-Length` header can lead to unbounded chunked file uploads and a denial of service (bsc#1261447). - CVE-2026-34230: rack: quadratic complexity when processing of wildcard `Accept-Encoding` headers can lead to a denial of service (bsc#1261388). - CVE-2026-34830: rack: improper sanitization of the `X-Accel-Mapping` request header can lead to the exposure of unintended files via `X-Accel-Redirect` (bsc#1261458). - CVE-2026-34831: rack: `Content-Length` header and body byte size mismatch when creating error responses can lead to incorrect HTTP response framing (bsc#1261466). Other updates and bugfixes: - Fix ReDoS in `Addressable`. - Fix out-of-bounds read in `rdiscount`.

References

Community reviews

Loading reviews…

Exploitation evidence

Description

Technical details

References

Community reviews

Related threats