Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed Savane 3.14-3.17 instance
-
DeliveryEnumerate file.php endpoint and authorization parameter structure
-
ExploitCraft HTTP request with manipulated untrusted authorization parameter
-
ExecutionServer evaluates tainted parameter as authoritative in access check
-
PersistAuthorization bypass grants access to restricted file
-
ImpactAttacker retrieves disclosed file content
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Incorrect behavior order
|
| Exploitation Conditions | The vulnerability is triggered through an HTTP request to the frontend/php/file.php endpoint in any Savane 3.14-3.17 deployment. No authentication is required (CVSS PR:N confirmed). The specific exploitation condition is that the authorization logic at lines 113 and 123 of file.php consumes a user-supplied HTTP parameter as a trust anchor rather than deriving authorization state exclusively from validated server-side session data. Exploitation is limited by High attack complexity (AC:H) - the attacker must know or enumerate the correct parameter name and value structure to influence the authorization outcome, making this unsuitable for blind mass-scanning. Impact is bounded to low confidentiality disclosure (C:L) of files accessible through that endpoint; no write capability or service disruption is possible through this vector. Deployments that do not expose the file download endpoint to untrusted networks are materially less exposed. |
| Impact | The overall risk signal is low-to-moderate. The NVD CVSS base score of 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) reflects a network-reachable, zero-privilege attack surface but tempers it with High attack complexity and only Low confidentiality impact - no integrity or availability consequence is claimed. No EPSS score is available in the provided data, so exploitation probability cannot be quantified precisely. The vulnerability is not listed in CISA KEV, and no public POC or exploit code was identified in the references. The FSF has issued a public acknowledgment, and the hacktron.ai and mallory.ai references suggest independent security researcher discovery. Taken together, this is a real vulnerability with narrow but confirmed impact (information disclosure from a file-access bypass), not a critical priority - but Savannah hosts sensitive GNU project infrastructure, raising the organizational value of targeted exploitation above what raw CVSS implies. The AC:H rating credibly limits mass-automated exploitation. |
| Exploit ScenarioDerived | An unauthenticated attacker with HTTP access to a Savane 3.14-3.17 instance crafts a request to frontend/php/file.php with a manipulated authorization parameter that the server-side logic accepts as trusted, substituting their own value for the expected session-derived authorization context. The server evaluates the tainted parameter in the access check at lines 113 or 123, concludes access is permitted, and returns a file from a restricted project that the attacker would not otherwise be authorized to retrieve. No public POC code has been identified; the AC:H CVSS rating indicates the attacker must have specific knowledge of the parameter structure or target file identifiers to succeed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 22, 2026
Information disclosure in GNU Savane's file-serving layer (frontend/php/file.php) allows network-accessible, unauthenticated remote attackers to bypass file authorization controls by supplying untrusted user-controlled data that the application incorrectly treats as authoritative in its access decision logic. Affected installations span Savane 3.14 through 3.17, confirmed by EUVD-2026-38135 and acknowledged via an FSF public statement. No public exploit has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog, though the AC:H CVSS rating suggests non-trivial exploitation rather than a trivially automated mass-scan scenario.
RemediationAI
No vendor-released patch with an exact fix version has been identified from available data at time of analysis. Operators should monitor the FSF statement at https://www.fsf.org/news/statement-regarding-gnu-savannah-security-reports and the upstream cgit repository for a patched release. As compensating controls: restrict HTTP access to frontend/php/file.php via web server ACLs or WAF rules, limiting access to authenticated sessions only at the network layer (trade-off: may break legitimate anonymous file downloads if that is an intended feature); audit and harden the PHP authorization logic at lines 113 and 123 of file.php to replace user-supplied parameters with server-side session-derived values before making access decisions; and enable detailed logging on that endpoint to detect anomalous parameter manipulation during the interim period. The VulDB advisory at https://vuldb.com/vuln/372570 may contain additional remediation guidance as it is updated.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GNU Savane is the PHP-based project management platform powering GNU Savannah, the free software hosting service operated by the Free Software Foundation. The flaw is localized to frontend/php/file.php at lines 113 and 123 in the release-3.17 branch, as confirmed by direct source references to the cgit repository. CWE-696 (Incorrect Behavior Order) describes a situation where the software performs related behaviors in the wrong sequence - here, user-controlled HTTP input is consumed as part of an authorization decision before it has been validated or replaced with server-side authoritative session data. CPE cpe:2.3:a:gnu:savane:*:*:*:*:*:*:*:* covers the affected product family. The consequence is that an attacker who correctly manipulates the relevant request parameter can circumvent file-level access restrictions, leading to limited confidentiality disclosure aligned with the C:L CVSS metric.
Know when Savane 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
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Network-reachable PHP endpoint; AC:H because exploitation requires knowledge of specific untrusted parameter structure; only low confidentiality disclosure with zero integrity or availability impact.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
GNU Savannah Administration Savane through 3.17 uses untrusted data as part of authorization.
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.
An issue in GNU Savane v.3.12 and before allows a remote attacker to escalate privileges via the form_id in the form_hea
An issue was discovered in GNU Savane v.3.13 and before, allows a remote attacker to execute arbitrary code and escalate
Insecure Direct Object Reference (IDOR) in GNU Savane v.3.12 and before allows a remote attacker to delete arbitrary fil
Cross Site Request Forgery vulnerability in GNU Savane v.3.12 and before allows a remote attacker to escalate privileges
EUVD-2026-38135
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB