Cribl incident
OAuth secret expressions fail to resolve during authentication after 4.20.0 upgrade
Resolved after 2 days 4 hours, on September 16, 2026.
Mitigated: We have identified the issue affecting OAuth secret expressions following the 4.20.0 upgrade and published a Known Issue with a workaround. Customers experiencing authentication failures can follow the documented workaround. Known Issue can be found here: https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-45304
Update timeline
- investigating Sep 16, 2026, 02:52 PM UTC
We are currently investigating this issue.
- investigating Sep 16, 2026, 03:33 PM UTC
Investigating: We are continuing to investigate an issue that may prevent OAuth secret expressions on Microsoft Sentinel destinations from resolving during authentication following the 4.20.0 upgrade.
- investigating Sep 16, 2026, 04:34 PM UTC
Update: We are continuing our investigation regarding this issue.
- identified Sep 16, 2026, 05:44 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 16, 2026, 05:57 PM UTC
We have published a known issue with a workaround for this issue. See https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-45304
- monitoring Sep 16, 2026, 06:23 PM UTC
Mitigated: We have identified the issue affecting OAuth secret expressions following the 4.20.0 upgrade and published a Known Issue with a workaround. Customers experiencing authentication failures can follow the documented workaround. Known Issue can be found here: https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-45304
- resolved Sep 18, 2026, 07:41 PM UTC
This incident has been resolved.
Your product runs on more than Cribl
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services