# CVE-2026-124037: Information exposure in Flock Safety Platform public access-list sign-up


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-496f-rcq4-w2g9

## What is CVE-2026-124037?

CVE-2026-124037 is a high-severity vulnerability in Flock Safety Platform, published on 10 Nov 2026. 

### Official description

An information exposure flaw in the public access-list sign-up feature of the Flock Safety Platform, present from 2026-06-23 to 2026-10-22, allowed a remote, unauthenticated attacker who had a community's public sign-up link and a registered vehicle's license plate to retrieve that registrant's name, email address, home address and approval status. Each lookup required solving a CAPTCHA. No license plate reader detections, images or video were exposed. Flock remediated the issue in the hosted service on 2026-10-22; no customer action is required.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-124037 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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