OAuth secrets containing C.* expressions fail to resolve during authentication
Incident Lifecycle
Incident Timeline
Monitoring
A fix has been implemented and we are monitoring the results.
Aug 21, 2026 at 1:49 AM UTC
Identified
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 o...
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 o...
Aug 21, 2026 at 1:47 AM UTC
Identified
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 th...
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 th...
Aug 21, 2026 at 1:00 AM UTC
Identified
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 th...
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 th...
Aug 21, 2026 at 12:00 AM UTC
Identified
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 th...
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 th...
Aug 20, 2026 at 11:10 PM UTC
Identified
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 th...
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 th...
Aug 20, 2026 at 10:00 PM UTC
Identified
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 th...
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 th...
Aug 20, 2026 at 9:02 PM UTC
Identified
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 th...
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 th...
Aug 20, 2026 at 9:01 PM UTC
Identified
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.
Next Update: In 1 hour or as soon as new information becomes available.
Aug 20, 2026 at 8:01 PM UTC
Identified
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.
Next Update: In 1 hour or as soon as new information becomes available.
Aug 20, 2026 at 7:12 PM UTC
Identified
The issue has been identified and a fix is being implemented.
Aug 20, 2026 at 6:13 PM UTC
Was your business affected by this Cribl outage?
Follow Cribl and route available status alerts to email or a team channel.