CVE-2026-5458: Use of Hard-coded Cryptographic Key in Noelse Individuals & Pro App
CVE-2026-5458 is a medium severity vulnerability in the Noelse Individuals & Pro App for Android versions up to 2. 1. 7. It involves the use of a hard-coded cryptographic key within the app's code, specifically related to the SEGMENT_WRITE_KEY argument in the file com/reactnative/antelop/BuildConfig. java. Exploitation requires local access to the device. The vendor has not responded to the disclosure, and no official patch or remediation guidance is currently available. The vulnerability could potentially allow attackers with local access to misuse the cryptographic key, but no known exploits are reported in the wild.
AI Analysis
Technical Summary
This vulnerability concerns the presence of a hard-coded cryptographic key in the Noelse Individuals & Pro App (up to version 2.1.7) on Android. The issue is located in the component com.afone.noelse, specifically in the file com/reactnative/antelop/BuildConfig.java, where the SEGMENT_WRITE_KEY argument is manipulated to use a fixed cryptographic key. The attack vector requires local access, and the vulnerability has been publicly disclosed with exploit code available. The vendor has not provided any response or patch, and no cloud service remediation applies as this is a local app vulnerability.
Potential Impact
The use of a hard-coded cryptographic key can weaken the security of cryptographic operations within the app, potentially allowing an attacker with local access to compromise data confidentiality or integrity related to the affected component. However, the impact is limited by the requirement for local access and the absence of known active exploitation in the wild. The CVSS score of 4.8 reflects a medium severity level.
Mitigation Recommendations
No official patch or remediation is currently available from the vendor, and the vendor has not responded to the disclosure. Users should avoid running the affected versions on untrusted devices or environments where local access by attackers is possible. Monitor vendor channels for any future updates or patches. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-5458: Use of Hard-coded Cryptographic Key in Noelse Individuals & Pro App
Description
CVE-2026-5458 is a medium severity vulnerability in the Noelse Individuals & Pro App for Android versions up to 2. 1. 7. It involves the use of a hard-coded cryptographic key within the app's code, specifically related to the SEGMENT_WRITE_KEY argument in the file com/reactnative/antelop/BuildConfig. java. Exploitation requires local access to the device. The vendor has not responded to the disclosure, and no official patch or remediation guidance is currently available. The vulnerability could potentially allow attackers with local access to misuse the cryptographic key, but no known exploits are reported in the wild.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability concerns the presence of a hard-coded cryptographic key in the Noelse Individuals & Pro App (up to version 2.1.7) on Android. The issue is located in the component com.afone.noelse, specifically in the file com/reactnative/antelop/BuildConfig.java, where the SEGMENT_WRITE_KEY argument is manipulated to use a fixed cryptographic key. The attack vector requires local access, and the vulnerability has been publicly disclosed with exploit code available. The vendor has not provided any response or patch, and no cloud service remediation applies as this is a local app vulnerability.
Potential Impact
The use of a hard-coded cryptographic key can weaken the security of cryptographic operations within the app, potentially allowing an attacker with local access to compromise data confidentiality or integrity related to the affected component. However, the impact is limited by the requirement for local access and the absence of known active exploitation in the wild. The CVSS score of 4.8 reflects a medium severity level.
Mitigation Recommendations
No official patch or remediation is currently available from the vendor, and the vendor has not responded to the disclosure. Users should avoid running the affected versions on untrusted devices or environments where local access by attackers is possible. Monitor vendor channels for any future updates or patches. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-04-02T22:23:25.416Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69cf69120a160ebd92df90e5
Added to database: 4/3/2026, 7:15:30 AM
Last enriched: 4/3/2026, 7:30:27 AM
Last updated: 4/3/2026, 10:09:03 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.