Uncontrolled XML entity expansion in the Flock Installer app for Android
- Exploited
- No known exploitation
- Fix
- Fixed in 2.35.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.35.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 1/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Flock Installer app for Android has an uncontrolled XML entity expansion flaw that lets an attacker with a valid technician account, from an adjacent network and while controlling or impersonating the camera being set up, crash the app on older Android releases by returning a camera configuration response with nested XML entity declarations. Exploitation requires user action, and the flaw does not allow reading or changing data on the device.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
An uncontrolled XML entity expansion vulnerability in the Flock Installer app for Android before version 2.35.0 allows an attacker who has a valid technician account and controls or impersonates the camera being set up to crash the app, on devices running Android 10, 11 or 12, by returning a camera configuration response that contains nested XML entity declarations. The vulnerability does not allow the attacker to read or change data on the device, and no customer license plate, video or location data is exposed. Android 13 and later reject the response. The issue is fixed in version 2.35.0; update to 2.35.0 or later.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity1/10CVSS 1.0
- No patch0/5No signal
What would change the score
- Would score about 56 if added to CISA KEV
- Would score about 51 if CISA's SSVC rates exploitation active
- Would score about 23 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.35.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124038 (Uncontrolled XML entity expansion in the Flock Installer app for Android), 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-124038 (entry last updated 2026-11-10): Affected: - Flock Flock Installer app: fixed in 2.35.0 Fixed versions: 2.35.0. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-124038 is not listed as of cve.now's last read. This KEV status is for CVE-2026-124038 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-124038 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-124038.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Flock Flock Installer app
fixed in 2.35.0
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124038
Is CVE-2026-124038 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: cve.now feed data
Which versions are affected by CVE-2026-124038?
Flock Installer app: before 2.35.0.Source: cve.now feed data
How do I fix CVE-2026-124038?
Upgrade to a fixed version: 2.35.0.Source: cve.now feed data