CVE-2026-26379

MEDIUMNVD 6.5Elevated

6.5

Koha versions up to 25.11 contain a Server-Side Request Forgery (SSRF) vulnerability via the Z39.50/SRU server configuration. This allows authenticated attackers to perform internal network scanning and identify running services by analyzing server response times.

CVSS v3: 6.5
EG Score: 0.0(none)
EPSS: 7.5%
KEV: Not listed

Published

June 3, 2026

Last Modified

June 4, 2026

References (4)

cve@mitrehttps://g03m0n.github.io/
cve@mitrehttps://g03m0n.github.io/posts/cve-2026-26379/
cve@mitrehttps://github.com/Koha-Community/Koha
134c704f-9b21-4f2e-91b3-4a467353bcc0https://g03m0n.github.io/posts/cve-2026-26379/

Vendor Advisories for CVE-2026-26379(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

GHSA-7pjj-942q-wrwg
GitHub Security AdvisoriesMedium
An issue in Koha v.25.11 and before allows a remote attacker to execute arbitrary code via the...

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:47 UTCepss_batch
2026-06-05 22:47 UTCepss_batch
2026-06-05 06:10 UTCepss_batch
2026-06-05 06:10 UTCepss_batch
2026-06-03 18:55 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-26379?

CVE-2026-26379 is a medium vulnerability published on June 3, 2026. Koha versions up to 25.11 contain a Server-Side Request Forgery (SSRF) vulnerability via the Z39.50/SRU server configuration. This allows authenticated attackers to perform internal network scanning and identify running services by analyzing server response times.

When was CVE-2026-26379 disclosed?

CVE-2026-26379 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on June 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-26379 actively exploited?

CVE-2026-26379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-26379?

CVE-2026-26379 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.

How do I remediate CVE-2026-26379?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26379, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26379

Explore →

Is Your Infrastructure Affected by CVE-2026-26379?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-26379

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2026-26379(1)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)