cve.bz

CVE-2026-50188 getkirby kirby: CRLF Injection

6.9 mediumEPSS 0.4%Fix available

Medium (6.9) in getkirby kirby. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in getkirby/cms 4.9.4, 5.4.4.

On this page
Kirby is an open-source content management system. Prior to 4.9.4 and 5.4.4, Kirby sites and plugins using the Kirby Http Remote class, including Remote::request(), Remote::get(), and Remote::post(), to send outgoing HTTP requests with untrusted data in the headers option could allow newline characters in a header value to inject a separate unintended request header to the remote service. This issue is fixed in versions 4.9.4 and 5.4.4.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-93 Improper Neutralization of CRLF Sequences (CRLF Injection)
CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers (HTTP Request Splitting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • getkirby/cms (Packagist): fixed in 4.9.4, 5.4.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-50188 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-50188?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-50188?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-50188 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
getkirby kirby< 4.9.4
getkirby kirby>= 5.0.0, < 5.4.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4v4h-m2qq-ppgwPackagistgetkirby/cms<4.9.44.9.4
GHSA-4v4h-m2qq-ppgwPackagistgetkirby/cms>=5.0.0-alpha.1 <5.4.45.4.4

Attack patterns (CAPEC)

  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-31 Accessing/Intercepting/Modifying HTTP Cookies Likelihood: High · Severity: High
  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON