CVE-2026-5545: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-6g7g-56fm-f8mp
Share
CVSS 6.5
CWE-613 CWE-305
Published
Advisory Summary

CVE-2026-5545 is a MODERATE (CVSS 6.5) security vulnerability vulnerability (CWE-613: Insufficient Session Expiration) affecting Software libraries in the Maven ecosystem. The weakness occurs when according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". Remediation is available in the latest vendor maintenance releases.

CVE-2026-5545 at a Glance

CVE Identifier CVE-2026-5545
GHSA Identifier GHSA-6g7g-56fm-f8mp
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-613: Insufficient Session Expiration
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-5545

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-5545, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when it is in fact still using the connection authenticated for user1...

References

NVD — CVE-2026-5545 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-5545
hackerone.com/reports/3642555 WEB
https://hackerone.com/reports/3642555
curl.se/docs/cve-2026-5545.... WEB
https://curl.se/docs/CVE-2026-5545.html
curl.se/docs/cve-2026-5545.... WEB
https://curl.se/docs/CVE-2026-5545.json

Frequently Asked Questions

What is CVE-2026-5545?
CVE-2026-5545 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-613: Insufficient Session Expiration.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-5545?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-5545?
CVE-2026-5545 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N.
What CWE is associated with CVE-2026-5545?
CVE-2026-5545 is classified under CWE-613: Insufficient Session Expiration (According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.").
How can I check Maven dependencies for CVE-2026-5545?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6g7g-56fm-f8mp",
  "modified" : "2026-05-13T18:30:52Z",
  "published" : "2026-05-13T18:30:52Z",
  "aliases" : [ "CVE-2026-5545" ],
  "details" : "libcurl might in some circumstances reuse the wrong connection when asked to\ndo an authenticated HTTP(S) request after a Negotiate-authenticated one, when\nboth use the same host.\n\nlibcurl features a pool of recent connections so that subsequent requests can\nreuse an existing connection to avoid overhead.\n\nWhen reusing a connection a range of criteria must be met. Due to a logical\nerror in the code, a request that was issued by an application could\nwrongfully reuse an existing connection to the same server that was\nauthenticated using different credentials.\n\nAn application that first uses Negotiate authentication to a server with\n`user1:password1` and then does another operation to the same server asking\nfor any authentication method but for `user2:password2` (while the previous\nconnection is still alive) - the second request gets confused and wrongly\nreuses the same connection and sends the new request over that connection\nthinking it uses a mix of user1's and user2's credentials when it is in fact\nstill using the connection authenticated for user1...",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-5545"
  }, {
    "type" : "WEB",
    "url" : "https://hackerone.com/reports/3642555"
  }, {
    "type" : "WEB",
    "url" : "https://curl.se/docs/CVE-2026-5545.html"
  }, {
    "type" : "WEB",
    "url" : "https://curl.se/docs/CVE-2026-5545.json"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-305", "CWE-613" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-13T13:01:56Z"
  }
}