# Cribl: OAuth secrets containing C.* expressions fail to resolve during authentication - Impact (vendor’s label): major - Status: resolved - Started: 2026-08-20 18:13 UTC · Resolved: 2026-08-21 15:30 UTC · Duration: 21 h - Updates: 12 - [Vendor status page: https://stspg.io/9hqk6sx4mz4l](https://stspg.io/9hqk6sx4mz4l) - [Company: Cribl](https://rewindex.com/company/cribl.md) ## Timeline of updates - **identified** 2026-08-20 18:13 UTC: The issue has been identified and a fix is being implemented. - **identified** 2026-08-20 19:12 UTC: 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. - **identified** 2026-08-20 20:01 UTC: 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. - **identified** 2026-08-20 21:01 UTC: 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. - **identified** 2026-08-20 21:02 UTC: 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. - **identified** 2026-08-20 22:00 UTC: 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. - **identified** 2026-08-20 23:10 UTC: 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. - **identified** 2026-08-21 00:00 UTC: 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. - **identified** 2026-08-21 01:00 UTC: 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. - **identified** 2026-08-21 01:47 UTC: 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. - **monitoring** 2026-08-21 01:49 UTC: A fix has been implemented and we are monitoring the results. - **resolved** 2026-08-21 15:30 UTC: This incident has been resolved. ## Rewindex changes for this incident - 2026-08-20 18:13 UTC: [Major incident: OAuth secrets containing C.\* expressions fail to resolve during authentication](https://rewindex.com/change/iad11d569b090c7.md) --- Canonical: https://rewindex.com/company/cribl/incidents/q7qqczv6snl3 · Markdown: https://rewindex.com/company/cribl/incidents/q7qqczv6snl3.md · JSON: https://rewindex.com/api/v1/companies/cribl/incidents/q7qqczv6snl3 · Generated 2026-10-20T00:52:13.577Z