Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain device/app package
-
ExploitReverse-engineer app binary
-
ExecutionExtract hard-coded key
-
ImpactDecrypt protected data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Exploitation Conditions | Exploitation requires access to the installed 'Yorisou e Net' Android or iOS application (per CVSS AV:P, physical access to the device) so the attacker can inspect or reverse-engineer the app package to recover the embedded key. There is no authentication or user-interaction requirement beyond obtaining the app, but impact is limited to disclosure of the hard-coded key itself (C:L, no integrity/availability impact); the physical-access gating and lack of automatability substantially limit real-world risk. Any downstream damage depends on what data the recovered key protects, which the advisory does not specify. |
| Impact | All signals point to a low-priority issue. The vendor/JPCERT CVSS 3.0 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N = 2.4) requires physical access to the device/app and yields only low confidentiality impact (recovery of an embedded key), with no integrity or availability impact. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so this is 'no public exploit identified at time of analysis.' The realistic risk is that extracting a hard-coded cryptographic key could weaken protection of data the app encrypts, but exploitation is not automatable and is gated by device access. Note a discrepancy: the vector uses AV:P (physical), yet hard-coded-key extraction is typically achievable via local reverse-engineering of the installed app binary (AV:L) - the vendor scoping should be verified. Overall this is a genuinely low-severity, low-urgency finding rather than a high-CVSS-but-overstated case. |
| Exploit ScenarioDerived | An attacker with access to a device running the 'Yorisou e Net' Android or iOS app reverse-engineers the application package to extract the hard-coded cryptographic key embedded in the binary. With that key, the attacker could decrypt or forge data the app protects with it. No public exploit code is available and the CVSS vector indicates physical access with low confidentiality impact only. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Hard-coded cryptographic key material embedded in the Tohoku Electric Power 'Yorisou e Net' Android and iOS apps can be recovered by inspecting or reverse-engineering the installed application package, potentially exposing whatever data or service that key protects. Both mobile builds are affected (per the vendor CPE entries), and the CVSS vector indicates physical access to the device (AV:P) with no authentication (PR:N) and no user interaction (UI:N) required, so the practical gate is simply obtaining and analyzing the app rather than any remote precondition. Impact is confined to a low-confidence confidentiality loss (C:L, no integrity or availability effect) and the advisory does not specify what the recovered key protects downstream; all signals point to a low-priority issue, with no public exploit code identified at time of analysis and no EPSS or KEV data provided. The JVN advisory JVN93985674 is the primary coordinated-disclosure reference.
RemediationAI
No vendor-released patch was identified at time of analysis, and the references provide no fixed version number, so the JVN advisory (https://jvn.jp/en/jp/JVN93985674/) should be monitored for updated Android and iOS builds and for any statement of what the hard-coded key protects. Because the key is baked into the binary, anyone holding the app can extract it, and remediation ultimately requires the vendor to stop shipping static secrets: replace the embedded key with per-install or per-user credentials, move key material into the Android Keystore or iOS Keychain (hardware-backed where available), and, if the same key was used to protect or derive server-side secrets or signing material, rotate those server-side values - noting that rotation will break older app builds unless a forced-upgrade gate is enforced, which in turn can lock out users on outdated operating systems. In the interim, operators should monitor backend and API logs for anomalous use of the affected credentials (unexpected volume, geographies, or client characteristics) to detect abuse, accepting the usual false-positive burden of such alerting, and may add per-account rate limiting or session binding as a containment measure that trades off some user convenience. Client-side obfuscation, string encryption, and native-code packing raise the cost of static extraction but do not remove the flaw, since the key must be recoverable at runtime; they are therefore only a delaying control and should not substitute for key redesign. Individual users can do little beyond installing the latest store version when it becomes available and treating physical device access as a trust boundary.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-321, use of a hard-coded cryptographic key: secret key material is compiled into the shipped mobile package instead of being generated per install or held in a hardware-backed store. Mobile distribution makes this class of defect straightforwardly reachable - APK and IPA bundles are handed to every end user and can be decompiled or disassembled with commodity tooling (e.g., apktool, jadx, Ghidra, or Hopper), and static string/entropy scans or inspection of bundled keystores, PEM blobs, and native libraries routinely surface embedded secrets. The consequence is architectural rather than merely technical: because the key is static and identical across all installations, and cannot be changed without shipping a new app build, exposure for a single user generalizes to the entire installed base, and no client-side rotation is possible. This is why platform facilities such as the Android Keystore or the iOS Keychain/Secure Enclave are the intended alternative, providing per-device, non-exportable key material. The CVSS 3.0 vector AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yields a score of 2.4, and our independent re-scoring under CVSS 3.1 (AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) produces a comparably low rating; the low confidentiality impact reflects that the advisory does not establish what the key protects, so downstream risk cannot be quantified from the available data. No CWE beyond CWE-321 is implicated, and no public exploit code or active-exploitation signal was supplied.
Know when iOS gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Hard-coded key is recovered by reverse-engineering the locally installed app (AV:L rather than AV:P), no auth needed, yielding only low confidentiality disclosure of the key.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
Lifecycle Timeline
1DescriptionCVE.org
Smartphone application Tohoku Electric Power "Yorisou e Net" uses a hard-coded cryptographic key, which may allow an attacker to retrieve a hard-coded cryptographic key from the affected product.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Apple's kernel across all platforms (iOS, macOS, watchOS, visionOS, tvOS) contains a memory corruption vulnerability (CV
A use-after-free issue was addressed with improved memory management. Rated high severity (CVSS 7.8), this vulnerability
The DLSw implementation in Cisco IOS does not initialize packet buffers, which allows remote attackers to obtain sensiti
The issue was addressed with improved checks. Rated high severity (CVSS 7.0). Actively exploited in the wild (cisa kev)
AirKeyboard iOS App 1.0.5 contains a missing authentication vulnerability that allows unauthenticated attackers to type
Mobile Security Framework (MobSF) is a security research platform for mobile applications in Android, iOS and Windows Mo
A vulnerability in the Cisco IOx application hosting environment of multiple Cisco platforms could allow an authenticate
Arbitrary code execution in Jellyfin iOS GitHub Actions workflow. CVSS 10.0.
Memory corruption vulnerabilities in Apple's graphics texture processing engine across iOS, iPadOS, macOS, tvOS, visionO
Buffer overflow memory corruption in Apple file parsing components allows remote code execution across iOS 18.6, iPadOS
A use-after-free issue was addressed with improved memory management. Rated critical severity (CVSS 9.8), this vulnerabi
Cisco IOS 15.5(3)M on Integrated Services Router (ISR) 800, 819, and 829 devices allows remote attackers to cause a deni
EUVD-2026-86531
GHSA-2q7r-p8fq-p422
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB