CVE-2026-69127

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Kirby is an open-source content management system. Prior to 4.9.5 and from 5.0.0 through 5.5.1, the REST API error handler can return unsanitized PHP error messages that expose the full filesystem path of the Kirby installation to unauthenticated API users. This vulnerability affects all Kirby sites that have not disabled the REST API with the 'api' => false option. This issue is fixed in versions 4.9.5 and 5.5.2.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 7, 2026

Last Modified

September 16, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 58f819988436 (getkirby/kirby)

Patch available: getkirby/kirby 5.5.2 (contains commit 58f819988436)

https://github.com/getkirby/kirby/commit/58f819988436b31969078bc4655452dd48546451
github Patch Available

System path exposure from error messages in the REST API · Advisory · getkirby/kirby · GitHub

https://github.com/getkirby/kirby/security/advisories/GHSA-rf2p-vh74-7vvh

Vendor Advisories for CVE-2026-69127(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
getkirby/cms5.0.0 ... 5.5.1 (28 versions)5.5.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 17:33 UTCEG score recompute
  3. 2026-09-17 15:10 UTCEG score recompute
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 11:08 UTCEG score recompute
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 08:48 UTCEG score recompute
  8. 2026-09-14 08:19 UTCEG score recompute
  9. 2026-09-13 07:51 UTCEG score recompute
  10. 2026-09-12 07:24 UTCEG score recompute
  11. 2026-09-11 14:53 UTCEPSS rescore
  12. 2026-09-11 09:37 UTCEPSS rescore
  13. 2026-09-11 06:56 UTCEG score recompute
  14. 2026-09-09 06:00 UTCEG score recompute
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 17:43 UTCEG score recompute
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-06 09:57 UTCEG score recompute
  20. 2026-09-05 15:31 UTCEPSS rescore
  21. 2026-09-05 09:30 UTCEG score recompute
  22. 2026-09-04 09:02 UTCEG score recompute
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-03 05:59 UTCEG score recompute
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 49 more
  1. 2026-09-01 22:55 UTCEG score recompute
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-08-31 22:27 UTCEG score recompute
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 16:25 UTCEG score recompute
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-29 15:57 UTCEG score recompute
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 11:53 UTCEG score recompute
  11. 2026-08-27 07:50 UTCEG score recompute
  12. 2026-08-26 14:47 UTCEPSS rescore
  13. 2026-08-26 06:39 UTCEG score recompute
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-25 05:47 UTCEG score recompute
  16. 2026-08-23 04:52 UTCEG score recompute
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 04:25 UTCEG score recompute
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 03:55 UTCEG score recompute
  21. 2026-08-20 22:56 UTCEPSS rescore
  22. 2026-08-20 03:26 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 02:58 UTCEG score recompute
  25. 2026-08-18 13:49 UTCEPSS rescore
  26. 2026-08-18 13:49 UTCEPSS rescore
  27. 2026-08-18 02:07 UTCEG score recompute
  28. 2026-08-17 13:47 UTCEPSS rescore
  29. 2026-08-17 01:36 UTCEG score recompute
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 14:56 UTCEPSS rescore
  32. 2026-08-16 02:15 UTCEPSS rescore
  33. 2026-08-16 01:09 UTCEG score recompute
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-14 00:14 UTCEG score recompute
  36. 2026-08-13 22:00 UTCEPSS rescore
  37. 2026-08-12 23:46 UTCEG score recompute
  38. 2026-08-12 13:51 UTCEPSS rescore
  39. 2026-08-11 23:19 UTCEG score recompute
  40. 2026-08-11 22:25 UTCEG score recompute
  41. 2026-08-11 21:19 UTCEG score recompute
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-09 20:23 UTCEG score recompute
  44. 2026-08-09 13:47 UTCEPSS rescore
  45. 2026-08-08 19:56 UTCEG score recompute
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-07 19:28 UTCEG score recompute
  48. 2026-08-07 18:47 UTCEG score recompute
  49. 2026-08-07 18:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69127?
CVE-2026-69127 is a medium vulnerability published on August 7, 2026. Kirby is an open-source content management system. Prior to 4.9.5 and from 5.0.0 through 5.5.1, the REST API error handler can return unsanitized PHP error messages that expose the full filesystem path of the Kirby installation to unauthenticated API users. This vulnerability affects all Kirby…
When was CVE-2026-69127 disclosed?
CVE-2026-69127 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69127 actively exploited?
CVE-2026-69127 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.0% of all scored CVEs.
What is the CVSS score of CVE-2026-69127?
CVE-2026-69127 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-69127?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69127, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69127

Explore →

Is Your Infrastructure Affected by CVE-2026-69127?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.