A stored SQL injection vulnerability in Koha through 24.11.17, 25.05.12, 25.11.06, and 26.05.01 allows authenticated staff with the borrowers => edit_borrowers permission to cause a time-based denial of service by storing a SQL payload in a patron lang field. The value is concatenated raw into a subquery in Koha::AdditionalContents->search_for_display when an issue slip is printed for the affected patron. The 25-character column length limits exploitation to timing attacks; data extraction is not practical. The stored payload executes on each subsequent issue-slip print, scaling linearly with the SLEEP value and the number of slip-news rows.
CVE-2026-72610
Score 4.3 from GitHub Security Advisory published 2026-08-11. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 11, 2026
Last Modified
August 11, 2026
Advisory Details (2)
Auto-updated Aug 11, 2026Vendor Advisories for CVE-2026-72610(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 33× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 09:25 UTCEG score recompute
- 2026-08-20 09:25 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:52 UTCEG score recompute
- 2026-08-19 09:52 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 10:19 UTCEG score recompute
- 2026-08-18 10:19 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:45 UTCEG score recompute
- 2026-08-17 10:45 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:12 UTCEG score recompute
- 2026-08-16 11:12 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 11:39 UTCEG score recompute
- 2026-08-15 11:39 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 12:05 UTCEG score recompute
- 2026-08-14 12:05 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:32 UTCEG score recompute
Show 8 moreShow fewer
- 2026-08-13 12:32 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 12:59 UTCGHSA enrichment
- 2026-08-11 13:25 UTCEG score recompute
- 2026-08-11 13:25 UTCGHSA enrichment
- 2026-08-11 12:22 UTCEG score recompute
- 2026-08-11 11:42 UTCEG score recompute
- 2026-08-11 11:42 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-72610?
When was CVE-2026-72610 disclosed?
Is CVE-2026-72610 actively exploited?
What is the CVSS score of CVE-2026-72610?
How do I remediate CVE-2026-72610?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72610
Is Your Infrastructure Affected by CVE-2026-72610?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.