VulnerabilityPublished 25 Nov 2025

CVE-2025-64304: Fuji Television Network "FOD" App for Android · Use of Hard-coded Cryptographic Key

Affects Fuji Television Network "FOD" App for AndroidSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium : upgrade to 5.2.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score

4.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.2.0

CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Fuji Television Network "FOD" App for Android to 5.2.0.

Affected software

Product	Affected	Fixed in
Fuji Television Network, Inc. "FOD" App for Android	Affected <5.2.0	Fixed in 5.2.0

AI-suggested

To mitigate this vulnerability, organizations and users should immediately update the "FOD" app to version 5.2.0 or later, where the hard-coded key issue has been addressed. Developers should avoid embedding cryptographic keys directly in the app binary; instead, they should implement secure key management solutions such as using Android's Keystore system or retrieving keys securely from backend servers with proper authentication. Organizations should enforce mobile device management (MDM) policies to restrict local access and prevent unauthorized app tampering or reverse engineering. Regular security audits and static code analysis of mobile applications can help detect similar issues early. Additionally, educating users about the risks of installing apps from untrusted sources and maintaining device security hygiene will reduce the likelihood of local compromise. Monitoring for unusual app behavior or data access patterns can also help detect exploitation attempts.

Description

"FOD" App uses hard-coded cryptographic keys, which may allow a local unauthenticated attacker to retrieve the cryptographic keys.

Impact

For European organizations, the primary impact is the potential exposure of sensitive cryptographic keys embedded in the "FOD" app, which could lead to unauthorized access to encrypted data or services protected by these keys. Although the attack requires local access, compromised or lost devices in corporate or personal environments could be exploited to extract keys, leading to confidentiality breaches. This is particularly relevant for media companies, broadcasters, or enterprises using the app for content distribution or internal communications. The vulnerability does not affect data integrity or system availability, limiting the scope of damage. However, the exposure of cryptographic keys can facilitate further attacks such as man-in-the-middle interception or unauthorized content access. European organizations with employees or customers using the affected app versions are at risk, especially in sectors with high mobile device usage and less stringent device security controls.

References

Community reviews

Loading reviews…