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

**Summary:** _summary pending_
- Kind: Major incident · Label: major (vendor)
- Changed: 2026-08-20 18:13 UTC · Detected: 2026-10-19 18:33 UTC
- [Source: https://stspg.io/9hqk6sx4mz4l](https://stspg.io/9hqk6sx4mz4l)
- [Company: Cribl](https://rewindex.com/company/cribl.md)
- Versions: before (none: first archived) → after incident\_version:731/q7qqczv6snl3@7010c2a3374c
- Change 1 of 1 for this incident

Incident page (full timeline): [OAuth secrets containing C.\* expressions fail to resolve during authentication](https://rewindex.com/company/cribl/incidents/q7qqczv6snl3.md)
## What changed

**1. Added: Title**

```diff
+ OAuth secrets containing C.* expressions fail to resolve during authentication
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-08-20 18:13 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-08-21 15:30 UTC
```

**6. Added: Update** (identified) · 2026-08-20 18:13 UTC

```diff
+ The issue has been identified and a fix is being implemented.
```

**7. Added: Update** (identified) · 2026-08-20 19:12 UTC

```diff
+ 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.
```

**8. Added: Update** (identified) · 2026-08-20 20:01 UTC

```diff
+ 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.
```

**9. Added: Update** (identified) · 2026-08-20 21:01 UTC

```diff
+ 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.
```

**10. Added: Update** (identified) · 2026-08-20 21:02 UTC

```diff
+ 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.
```

**11. Added: Update** (identified) · 2026-08-20 22:00 UTC

```diff
+ 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.
```

**12. Added: Update** (identified) · 2026-08-20 23:10 UTC

```diff
+ 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.
```

**13. Added: Update** (identified) · 2026-08-21 00:00 UTC

```diff
+ 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.
```

**14. Added: Update** (identified) · 2026-08-21 01:00 UTC

```diff
+ 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.
```

**15. Added: Update** (identified) · 2026-08-21 01:47 UTC

```diff
+ 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.
```

**16. Added: Update** (monitoring) · 2026-08-21 01:49 UTC

```diff
+ A fix has been implemented and we are monitoring the results.
```

**17. Added: Update** (resolved) · 2026-08-21 15:30 UTC

```diff
+ This incident has been resolved.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-08-20 18:13 UTC | Major incident: OAuth secrets containing C.\* expressions fail to resolve during authentication (this change) | major |

All Cribl changes: [timeline](https://rewindex.com/company/cribl/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/iad11d569b090c7 · Markdown: https://rewindex.com/change/iad11d569b090c7.md · JSON: https://rewindex.com/api/v1/changes/iad11d569b090c7 · Generated 2026-10-20T00:01:11.145Z