CVE-2026-12616

Source
https://cve.org/CVERecord?id=CVE-2026-12616
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-12616.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-12616
Published
2026-06-29T13:23:38.967Z
Modified
2026-07-15T01:48:49.955570924Z
Severity
  • 6.9 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
[none]
Details

The /v1/upload/sbom endpoint extracts the iss claim from the attacker-supplied JWT with signature verification disabled, then interpolates that string into three log statements before any validation gate. Because the configured log format ("%(asctime)s - %(name)s - %(levelname)s - %(message)s") renders newlines literally, an unauthenticated attacker can forge log records that are byte-for-byte indistinguishable from PIA's genuine "Successfully authenticated project" message. PIA is an authentication broker whose logs are explicitly relied upon for incident response (DESIGN.md ยง5.4 lists "Token verifications" and "Errors" as events to log), so the ability to plant fake auth-success entries directly undermines the audit trail the service exists to produce.

Database specific
{
    "cna_assigner": "eclipse",
    "cwe_ids": [
        "CWE-117"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/12xxx/CVE-2026-12616.json"
}
References

Affected packages

Git / github.com/eclipse-csi/pia

Affected ranges

Type
GIT
Repo
https://github.com/eclipse-csi/pia
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Last affected
Database specific
{
    "source": "AFFECTED_FIELD",
    "extracted_events": [
        {
            "introduced": "0"
        },
        {
            "last_affected": "0.2.1"
        }
    ]
}

Affected versions

v0.*
v0.1.0
v0.2.0
v0.2.1

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-12616.json"