# CVE-2026-119736: Attendo Admin Android 3.0.13 Hard-coded MQTT Broker Credentials


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-68mx-c8hg-wjhw

## What is CVE-2026-119736?

CVE-2026-119736 is a high-severity vulnerability in Attendo (formerly Petpooja Payroll), published on 2 Nov 2026. 

### Official description

Attendo (formerly Petpooja Payroll) Admin Android application version 3.0.13 and earlier contains a hard-coded credentials vulnerability that allows attackers to extract production MQTT broker credentials by decompiling the APK's bundled Flutter configuration assets such as production.json and device-command configuration files. Attackers can use the recovered credentials to authenticate to the production MQTT broker over TCP 1883, access messaging topics containing employee attendance records, personal identifiers, Base64-encoded photographs, device telemetry, and authentication material, and publish messages to those topics, resulting in exposure of sensitive data and potential unauthorized message injection.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-119736 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119736 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119736 is a high-severity vulnerability in Attendo (formerly Petpooja Payroll), published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119736 exists.

Affected product: Attendo (formerly Petpooja Payroll). 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-119736/ (Markdown: https://insights.sbomify.com/CVE-2026-119736/index.md)
```

## Sources

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

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