# May Security Release

**URL:** <https://forum.getkirby.com/t/may-security-release/35411>\
**Category:** Announcements\
**Tags:** v4, v5\
**Created:** [May 19, 2026, 10:46am UTC](https://forum.getkirby.com/t/may-security-release/35411 "2026-05-19T10:46:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bastianallgeier](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/bastianallgeier/32/7569_2.png) [@bastianallgeier](https://forum.getkirby.com/u/bastianallgeier)\
**Post date:** [May 19, 2026, 10:46am UTC](https://forum.getkirby.com/t/may-security-release/35411/1 "2026-05-19T10:46:30Z")

</div>

Hey everyone,

as announced last week, today we are releasing our security release(s) for May.

- [Release 5.4.1 · getkirby/kirby · GitHub](https://github.com/getkirby/kirby/releases/tag/5.4.1)
- [Release 4.9.1 · getkirby/kirby · GitHub](https://github.com/getkirby/kirby/releases/tag/4.9.1)

You will find all the details about the security issues and fixes in the release notes for 5.4.1, and they will also apply to the 4.9.1 backport. We recommend this update to all users.

We’ve talked plenty about the situation in the past weeks and, as suggested by @nilshoerrmann and @johannahoerrmann, followed up with an article about the security situation on our blog: [Kirby & Security | Kirby CMS](https://getkirby.com/buzz/security-update). This will hopefully help provide a better picture for your clients and manage their expectations and concerns.

If there will be more AI or human assisted security reports until then, the next security release will follow on June 17th.

As always, let us know if you have any questions!

---

<div class="post-metadata">

**Author:** ![ahmetbora](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/ahmetbora/32/11671_2.png) [@ahmetbora](https://forum.getkirby.com/u/ahmetbora)\
**Post date:** [May 20, 2026, 10:30am UTC](https://forum.getkirby.com/t/may-security-release/35411/2 "2026-05-20T10:30:24Z")

</div>

Pinned globally on May 20, 2026, 10:30am UTC



---

<div class="post-metadata">

**Author:** ![bastianallgeier](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.getkirby.com/bastianallgeier/32/7569_2.png) [@bastianallgeier](https://forum.getkirby.com/u/bastianallgeier)\
**Post date:** [May 20, 2026, 3:09pm UTC](https://forum.getkirby.com/t/may-security-release/35411/3 "2026-05-20T15:09:07Z")

</div>

If you’ve tried to update via composer today you’ve probably already realised that the `symfony/yaml` package had a security release a couple hours after our release. Perfect timing We don’t consider this an immediate threat for our users, because we are not using the yaml parser to parse user input directly. But you won’t be able to update via composer without some nasty temporary hacks and that’s reason enough to already release two more patch releases:

- [Release 5.4.2 · getkirby/kirby · GitHub](https://github.com/getkirby/kirby/releases/tag/5.4.2)
- [Release 4.9.2 · getkirby/kirby · GitHub](https://github.com/getkirby/kirby/releases/tag/4.9.2)
