# CVE-2026-124036: Cross-organization access to saved-search alerts in FlockOS


- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-g4xg-gv8m-6gxf

## What is CVE-2026-124036?

CVE-2026-124036 is a high-severity vulnerability in FlockOS, published on 10 Nov 2026. 

### Official description

Missing authorization checks in the visual alert feature of FlockOS, Flock's hosted public safety platform, prior to 2026-09-28, allowed an authenticated user with permission to manage saved searches in their own organization to read, modify or delete another organization's saved-search alerts and change their recipients, given the alert's identifier, and to create alerts attributed to another organization. Flock remediated the issue in the hosted service on 2026-09-28; no customer action is required.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-124036 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124036 is a high-severity vulnerability in FlockOS, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124036 in the wild and no public exploit code.

Affected product: FlockOS. 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-124036/ (Markdown: https://insights.sbomify.com/CVE-2026-124036/index.md)
```

## Sources

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

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