VulnerabilityPublished 5 Nov 2025Updated 7 Nov 2025

CVE-2025-56232: GOG Galaxy 2.0.0.2 suffers from Missing SSL Certificate Validation

Source GCVE Database

Compare

Authoritative record:CVE-2025-56232· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium.

Data as of 4 Nov 2026, 18:39 UTC

CVSS 3.1 base score

6.8Medium

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 4 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-fwcq-rjr3-7rr9

What to do

AI-suggested

Users should exercise caution when updating GOG Galaxy 2.0.0.2, especially on untrusted networks. Monitor vendor advisories for updates or patches addressing this vulnerability. Until a fix is released, avoid using untrusted networks or intermediaries for updates.

Description

GOG Galaxy version 2.0.0.2 has a vulnerability due to missing SSL certificate validation. This flaw allows an attacker with control over the local network, DNS, or a proxy to perform man-in-the-middle attacks, potentially intercepting update requests and substituting legitimate installer or update files with malicious ones.

Impact

An attacker who can intercept network traffic can exploit this vulnerability to perform man-in-the-middle attacks, potentially delivering malicious installer or update files to the victim. This compromises the confidentiality of the update process and could lead to execution of unauthorized code. The integrity impact is low, and availability is not affected. There is no evidence of active exploitation in the wild.

Summary

The vulnerability identified as CVE-2025-56232 affects GOG Galaxy 2.0.0.2 and is characterized by the absence of SSL certificate validation during update processes. This security gap enables attackers positioned within the local network, DNS infrastructure, or proxy to intercept communications and replace update packages with malicious payloads. The CVSS 3.1 base score is 6.8, reflecting a medium severity with high confidentiality impact, low integrity impact, and no availability impact.

CWE-599Missing Validation of OpenSSL Certificate (opens in a new tab)
Variant weakness
The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.
Architecture and Design
Ensure that proper authentication is included in the system design.
Implementation
Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2026, 18:39 UTC

WeaknessesCWE-599

Technical details

References

Community reviews

Related threats