# CVE-2026-5458: Noelse Individuals & Pro App com.afone.noelse BuildConfig.java hard-coded key

> Attackers with local access can exploit a hard-coded cryptographic key in the Noelse Android app to bypass security controls.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/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:** 3 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-r583-x83p-jgxx

## What is CVE-2026-5458?

CVE-2026-5458 is a medium-severity vulnerability in Noelse Individuals & Pro App, published on 3 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in Noelse Individuals & Pro App up to 2.1.7 on Android. This impacts an unknown function of the file com/reactnative/antelop/BuildConfig.java of the component com.afone.noelse. This manipulation of the argument SEGMENT_WRITE_KEY causes use of hard-coded cryptographic key
 . The attack needs to be launched locally. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-320

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


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

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

## Is CVE-2026-5458 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5458 is a medium-severity vulnerability in Noelse Individuals & Pro App, published on 3 Apr 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-5458 exists.

Affected product: Noelse Individuals & Pro 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-5458/ (Markdown: https://insights.sbomify.com/CVE-2026-5458/index.md)
```

## Sources

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

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