FastBee through 2.1.0 IDOR via /iot/product By-ID Endpoints
FastBee through 2.1.0 lets non-owners obtain MQTT credentials via the product detail and getMqttConnectData endpoints. CVSS scores it 8.7 (high); no vendor rating or fix is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects FastBee v2.1.0
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
CVE-2026-121556 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects FastBee; a fix or patch is referenced.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- 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: total
Summary
FastBee, an IoT platform, is affected by an insecure direct object reference flaw in its product endpoints that lets logged-in users reach other tenants' product data. An attacker could read or change another tenant's MQTT credentials and configuration or delete their products, compromising confidentiality, integrity, and availability.
Read the original description
FastBee through 2.1.0 contains an insecure direct object reference vulnerability in ProductController that allows authenticated tenant users to access other tenants' products by supplying their product IDs. Attackers can enumerate sequential product IDs to read MQTT account, password, and secret values, overwrite product configuration including tenant_id, or delete products with cascading rows.
What to do
Check whether your setup matches what the bug needs.
Affects FastBee v2.1.0Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- beecue FastBee
through 2.1.0
Evidence 7
- Patch
- Report
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121556
Is CVE-2026-121556 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
What does this mean?
The product detail endpoint and the getMqttConnectData endpoint return MQTT credentials to users who do not own the product. The flaw is an insecure direct object reference through the /iot/product By-ID endpoints.Source: github.com
Which versions are affected by CVE-2026-121556?
FastBee: through 2.1.0.Source: cve.now feed data
Am I affected, and how do I check?
The listed range runs from the first release through FastBee 2.1.0 from beecue. To check a installation, compare its version against that range, since the advisory tests against v2.1.0.Source: github.com
How do I fix CVE-2026-121556?
The checked facts name no fixed release, so no upgrade target is confirmed. Releases after 2.1.0 fall outside the listed range, but the project's release notes should be checked for a confirmed fix.Source: github.com