# CVE-2026-112292: CheckCle through 1.6.0 Missing Authorization via Empty PocketBase API Rules

> Unauthenticated attackers can read, modify, or delete monitoring records and steal secrets due to missing authorization in CheckCle.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-52m4-ffr8-945g

## What is CVE-2026-112292?

CVE-2026-112292 is a critical missing authorization vulnerability in operacle checkcle, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CheckCle through 1.6.0 contains a missing authorization vulnerability that allows unauthenticated attackers to read, modify and delete records because shipped PocketBase collections use empty API rules. Attackers can query /api/collections/<name>/records endpoints to steal server_token values and alert_configurations secrets, disable alerting, alter status pages, or delete monitoring data.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-112292?


## How do I fix CVE-2026-112292?

No fix has been published for CVE-2026-112292 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112292 being exploited?

There is no known exploitation of CVE-2026-112292 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112292 and fix it if it is affected.

What it is: CVE-2026-112292 is a critical missing authorization vulnerability in operacle checkcle, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112292 in the wild and no public exploit code.

Affected product: operacle checkcle. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112292/ (Markdown: https://insights.sbomify.com/CVE-2026-112292/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112292
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112292
- OSV: https://osv.dev/vulnerability/CVE-2026-112292

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112292/
Summaries are generated and may contain mistakes; the official description above is the record.