CVE-2025-69206VulnerabilityPublished 29 Dec 2025

CVE-2025-69206: HemmeligOrg Hemmelig.app · Server-Side Request Forgery (SSRF)

Affects HemmeligOrg Hemmelig.appSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 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 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.3.3

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: 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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 29 Dec 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 hemmeligorg/Hemmelig.app to 7.3.3.

Affected software

Product	Affected	Fixed in
GitHubhemmeligorg/Hemmelig.app`pkg:github/hemmeligorg/Hemmelig.app`Other threats	Affected <7.3.3	Fixed in 7.3.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Hemmelig.app to version 7.3.3 or later immediately to apply the official patch that corrects the webhook URL validation and blocks SSRF bypass techniques. 2. Implement network segmentation and strict firewall rules to limit the Hemmelig server’s ability to initiate HTTP requests to sensitive internal resources, reducing the impact of any SSRF exploitation. 3. Monitor application logs and network traffic for unusual outbound HTTP requests originating from Hemmelig.app servers, which could indicate attempted SSRF exploitation. 4. Enforce strong authentication and access controls on the Hemmelig.app platform to minimize the risk of unauthorized users gaining the low-level privileges needed to exploit this vulnerability. 5. Conduct internal security assessments and penetration tests focusing on SSRF and related web vulnerabilities to identify and remediate similar weaknesses in other applications. 6. Educate users about the importance of applying updates promptly and maintaining vigilance for suspicious activity within secure messaging platforms.

Description

Hemmelig is a messing app with with client-side encryption and self-destructing messages. Prior to version 7.3.3, a Server-Side Request Forgery (SSRF) filter bypass vulnerability exists in the webhook URL validation of the Secret Requests feature. The application attempts to block internal/private IP addresses but can be bypassed using DNS rebinding or open redirect services. This allows an authenticated user to make the server initiate HTTP requests to internal network resources. Version 7.3.3 contains a patch for the issue.

Impact

For European organizations, this SSRF vulnerability poses a moderate risk primarily to confidentiality. Attackers with valid user credentials could exploit the flaw to access internal network resources that are normally shielded from external access. This could lead to unauthorized information disclosure from internal services, such as intranet portals, internal APIs, or management interfaces. Although the vulnerability does not directly compromise message integrity or availability of the Hemmelig.app service, the ability to reach internal endpoints could facilitate further lateral movement or reconnaissance within the network. Organizations in sectors handling sensitive communications—such as government, finance, healthcare, and critical infrastructure—may face increased risk if internal systems are exposed via SSRF. The impact is somewhat mitigated by the requirement for authentication and the absence of known active exploits, but the potential for internal data leakage remains a concern. Prompt patching is essential to reduce exposure, especially in environments where Hemmelig.app is integrated into secure communication workflows.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (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

Affected software

Description

AI analysisMachine-generated, updated 30 Dec 2025, 23:31 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats