Rewindex

ChangesCriblOAuth secrets containing C.* expressions fail to resolve during authentication

Cribl: Major incident: OAuth secrets containing C.* expressions fail to resolve during authentication

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Cribl removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: OAuth secrets containing C.* expressions fail to resolve during authentication
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-08-20 18:13 UTC
AddedResolved time#5
Before: not present
After: 2026-08-21 15:30 UTC
AddedUpdateidentified#6
Before: not present
After: The issue has been identified and a fix is being implemented.
AddedUpdateidentified#7
Before: not present
After: We have identified the root cause of the issue impacting OAuth secret fields following the v4.19.1 release. Our engineering team is actively working on a resolution.If you are experiencing this issue or require assistance, please reach out to our support team at support@cribl.io. Next Update: In 1 hour or as soon as new information becomes available.
AddedUpdateidentified#8
Before: not present
After: We have identified the root cause of the issue impacting OAuth secret fields following the v4.19.1 release. Our engineering team is actively working on a resolution.If you are experiencing this issue or require assistance, please reach out to our support team at support@cribl.io. Next Update: In 1 hour or as soon as new information becomes available.
AddedUpdateidentified#9
Before: not present
After: We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at support@cribl.io. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.
AddedUpdateidentified#10
Before: not present
After: We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at support@cribl.io. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.
AddedUpdateidentified#11
Before: not present
After: We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at support@cribl.io. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.
AddedUpdateidentified#12
Before: not present
After: We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at support@cribl.io. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.
AddedUpdateidentified#13
Before: not present
After: We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at support@cribl.io. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.
AddedUpdateidentified#14
Before: not present
After: We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release and are preparing to deploy a new version to remediate the issue. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443). https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at support@cribl.io. Next Update: Will occur at the top of the hour or as soon as fix deployment begins.
AddedUpdateidentified#15
Before: not present
After: We are actively working on a resolution for the issue affecting OAuth secret fields following the v4.19.1 release. A fix has been prepared and will be deployed as part of a rolling upgrade. Your organization will be picked up for upgrade on a rolling basis between 01:45 and 05:45 UTC on August 21, 2026 (9:45 PM – 1:45 AM EDT, Aug 20–21). Once the upgrade begins for your tenant, it will take approximately 20 minutes to complete. For full details and temporary workarounds, please review our published Known Issue (CRIBL-44443): https://docs.cribl.io/results/?searchOption=known-issues&tickets=CRIBL-44443 If you have additional questions or require assistance, please contact our support team at support@cribl.io.
AddedUpdatemonitoring#16
Before: not present
After: A fix has been implemented and we are monitoring the results.
AddedUpdateresolved#17
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

Thursday, August 20

1 incident change

All Cribl changesCribl profileMarkdownJSON