# CVE-2026-4218: myAEDES App aedes.me.beta EngageBayUtils.java information disclosure

> Local attackers can manipulate the AUTH_KEY argument in EngageBayUtils.java to disclose sensitive information in the myAEDES Android app.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-79x7-8whp-c62c

## What is CVE-2026-4218?

CVE-2026-4218 is a low-severity vulnerability in myAEDES App, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in myAEDES App up to 1.18.4 on Android. Affected is an unknown function of the file aedes/me/beta/utils/EngageBayUtils.java of the component aedes.me.beta. Performing a manipulation of the argument AUTH_KEY results in information disclosure. The attack is only possible with local access. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-4218 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4218 is a low-severity vulnerability in myAEDES App, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4218 exists.

Affected product: myAEDES App. 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-4218/ (Markdown: https://insights.sbomify.com/CVE-2026-4218/index.md)
```

## Sources

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

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