CVE-2025-44017VulnerabilityPublished 2 Sep 2025

CVE-2025-44017: "Gunosy" App for Android · Insertion of sensitive information into sent data

Affects "Gunosy" App for AndroidSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 7.34.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

4.3Medium

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 2 Sep 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 2026-10-25.

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 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 "Gunosy" App for Android to 7.34.0.

Affected software

Product	Affected	Fixed in
Gunosy Inc. "Gunosy" App for Android	Affected <7.34.0	Fixed in 7.34.0

AI-suggested

1. Update the Gunosy app to version 7.34.0 or later, where the vulnerability has been addressed. 2. Educate users about the risks of clicking on untrusted or suspicious URLs, emphasizing caution with links received via email, messaging apps, or social media. 3. Implement network-level protections such as URL filtering and anti-phishing solutions to block access to known malicious or suspicious URLs that could exploit this vulnerability. 4. Monitor network traffic for unusual outbound requests from mobile devices that may indicate leakage of sensitive tokens. 5. Encourage the use of multi-factor authentication (MFA) for services accessed via the Gunosy app or related accounts to reduce the impact of stolen JWTs. 6. For organizations managing mobile devices, deploy Mobile Device Management (MDM) solutions to enforce app updates and restrict installation of untrusted applications. 7. Conduct regular security awareness training focusing on social engineering and phishing threats that could exploit this vulnerability. 8. Review and audit token lifetimes and revocation mechanisms within the app's backend to minimize the window of opportunity for attackers if tokens are compromised.

Description

"Gunosy" App contains a vulnerability where sensitive information may be included in the application's outbound communication. If a user accesses a crafted URL, an attacker may obtain the JWT (JSON Web Token).

Impact

For European organizations, the impact of CVE-2025-44017 depends largely on the prevalence of the Gunosy app among their employees or customers. If the app is used for news aggregation or content delivery within corporate environments, exposure of JWTs could lead to unauthorized access to user accounts, potentially leaking personal or organizational data. Although the vulnerability does not directly affect enterprise systems, compromised user tokens could be leveraged for lateral movement or social engineering attacks within organizations. Additionally, if the app is used in sectors handling sensitive information (e.g., media, communications, or marketing firms), the risk of data leakage increases. The medium severity and requirement for user interaction somewhat limit the threat, but targeted phishing campaigns exploiting this vulnerability could still pose a risk. Furthermore, GDPR considerations mean that any unauthorized access or data leakage involving European users could result in regulatory scrutiny and fines. Organizations should be aware of this vulnerability to prevent potential reputational damage and ensure compliance with data protection regulations.

References

jvn.jp/en/jp/JVN47404248/ (opens in a new tab)

Community reviews

Loading reviews…