| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 4.80 |
Summary
A vulnerability, which was classified as problematic, was found in GNU Savane up to 3.17. Affected by this vulnerability is an unknown functionality. The manipulation results in incorrect behavior order. This vulnerability is known as CVE-2026-56355. It is possible to launch the attack remotely. No exploit is available. A patch should be applied to remediate this issue.
Details
A vulnerability was found in GNU Savane up to 3.17. It has been classified as problematic. Affected is some unknown functionality. The manipulation with an unknown input leads to a incorrect behavior order vulnerability. CWE is classifying the issue as CWE-696. The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses. This is going to have an impact on confidentiality. CVE summarizes:
GNU Savannah Administration Savane through 3.17 uses untrusted data as part of authorization.
The advisory is available at cgit.git.savannah.gnu.org. This vulnerability is traded as CVE-2026-56355 since 06/20/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at cgit.git.savannah.gnu.org.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-38135). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.gnu.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Incorrect behavior orderCWE: CWE-696
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: cgit.git.savannah.gnu.org
Timeline
06/20/2026 CVE reserved06/21/2026 Advisory disclosed
06/21/2026 VulDB entry created
06/21/2026 VulDB entry last update
Sources
Vendor: gnu.orgAdvisory: cgit.git.savannah.gnu.org
Status: Confirmed
CVE: CVE-2026-56355 (🔒)
GCVE (CVE): GCVE-0-2026-56355
GCVE (VulDB): GCVE-100-372570
EUVD: 🔒
Entry
Created: 06/21/2026 05:43Updated: 06/21/2026 06:48
Changes: 06/21/2026 05:43 (62), 06/21/2026 06:48 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.

No comments yet. Languages: en.
Please log in to comment.