Skip to content

News

Kestra OSS authentication bypass: how to organise your response

A critical flaw in Kestra OSS lets an unauthenticated attacker run code, and CISA lists it as exploited. This article explains who is affected and how to organise the response.

  • Published on
Abstract pattern of navy and red shapes on a navy grid: the standard cover of an article about a security advisory.

This article was written automatically on 17 November 2026 from the information on this site and checked by automated rules; it was not reviewed by a person. Tell us if something is wrong

If your organisation runs Kestra OSS, a security advisory published on 27 June 2026 needs your attention. This article explains it in plain terms, so that you can decide who checks what, and in which order. It does not contain technical details of the flaw. Those are on the advisory page.

What the advisory says

The flaw is tracked as CVE-2026-49869. A CVE (Common Vulnerabilities and Exposures) identifier is a public reference number for one specific security weakness. The weakness is an authentication bypass in Kestra OSS, the open-source edition of the Kestra workflow platform. According to the sources, an unauthenticated remote attacker can use it to run code in the worker container. The worker is the part that carries out the tasks of your workflows.

The key facts are these:

  • Vendor and product: Kestra, Kestra OSS.
  • Affected versions: anything below 1.0.45, and versions from 1.1.0 up to, but not including, 1.3.21.
  • Severity: critical, with a CVSS score of 10.0. CVSS is a common scale from 0 to 10 for rating how serious a flaw is.
  • Exploitation: CISA, the United States cybersecurity agency, lists this flaw in its Known Exploited Vulnerabilities catalogue.

The full summary is in the PiLabs advisory on CVE-2026-49869. It is a summary of public sources, not an independent test.

Why it matters to your organisation

An authentication bypass means that a login check can be skipped. Remote code execution means that someone outside can make your system run instructions of their choosing. Together, and with no login needed, they describe a serious situation.

Workflow platforms are often trusted with a lot. They may hold access details for databases, file stores and other services, because their tasks need to reach them. A problem in the worker can therefore matter beyond the platform itself. The listing in the CISA catalogue means that exploitation has been observed. It is not only a theoretical risk.

How urgent this is for you depends on two things: whether you run an affected version, and who can reach the service over the network.

How to organise the response

Treat this as a short, planned piece of work with clear owners.

  1. Find out whether you use Kestra OSS. Ask the teams that run data jobs, automation and integrations. It is sometimes installed by one team without the wider organisation knowing.
  2. Check the version. Compare each installation with the affected ranges above. Do not rely on memory. Ask for the version to be read from the system.
  3. Note who can reach it. A service open to the internet needs a faster response than one reachable only from a closed internal network. Both still need the update.
  4. Follow the vendor's instructions. CISA's required action is to apply mitigations in accordance with the vendor's instructions, or to stop using the product if mitigations are not available. The Kestra security advisory contains the instructions and the list of fixed releases.
  5. Plan the update. Take a backup, test the new release if you can, agree a maintenance window and decide who confirms that the update worked.
  6. Look for signs of misuse. Ask for a review of logs and of unexpected workflow activity since the disclosure. If an exposed instance may have been reached, consider changing the credentials that its workflows use. This is a precaution, not a finding.

What to ask your supplier or your internal team

If an outside company runs Kestra for you, or an internal team does, a few direct questions give you a clear picture:

  • Which version is running in each environment, and when was it last checked?
  • Is the service reachable from the internet, and does it need to be?
  • When will the fixed release be installed, and who approves it?
  • Which credentials and systems can the worker reach?
  • Has anyone reviewed the logs for unusual activity?

Ask for written answers. They help if you need to report on the matter later, and they show where an owner is missing.

Where to read more

For the exact technical details, use the Kestra security advisory, the NVD (National Vulnerability Database) entry and the CISA Known Exploited Vulnerabilities catalogue. Pinet publishes summaries of public advisories on PiLabs, including the advisory on CVE-2026-49869, and offers cybersecurity consulting.

More

More news

All news

Have a question about this news?

Write to us. A consultant will answer.