CVE-2026-27629

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-8602 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

InvenTree is an Open Source Inventory Management System. Prior to version 1.2.3, insecure server-side templates can be hijacked to expose secure information to the client. When generating custom batch codes, the InvenTree server makes use of a customizable jinja2 template, which can be modified by a staff user to exfiltrate sensitive information or perform code execution on the server. This issue requires access by a user with granted staff permissions, followed by a request to generate a custom batch code via the API. Once the template has been modified in a malicious manner, the API call to generate a new batch code could be made by other users, and the template code will be executed with their user context. The code has been patched to ensure that all template generation is performed within a secure sandboxed context. This issue has been addressed in version 1.2.3, and any versions from 1.3.0 onwards. Some workarounds are available. The batch code template is a configurable global setting which can be adjusted via any user with staff access. To prevent this setting from being edited, it can be overridden at a system level to a default value, preventing it from being edited. This requires system administrator access, and cannot be changed from the client side once the server is running. It is recommended that for InvenTree installations prior to 1.2.3 the STOCK_BATCH_CODE_TEMPLATE and PART_NAME_FORMAT global settings are overridden at the system level to prevent editing.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 25, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Server Side Template Injection (SSTI) · Advisory · inventree/InvenTree · GitHub

https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 103 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 6 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 06:42 UTCEG score recompute
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-25 14:38 UTCEG score recompute
  10. 2026-10-24 23:33 UTCEG score recompute
  11. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-18 03:51 UTCEG score recompute
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-17 16:25 UTCEG score recompute
  21. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 72 more
  1. 2026-10-12 16:17 UTCEG score recompute
  2. 2026-10-11 19:59 UTCEG score recompute
  3. 2026-10-11 17:13 UTCEG score recompute
  4. 2026-10-11 14:44 UTCEG score recompute
  5. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-09 06:55 UTCOSV refresh
  9. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-09-19 13:33 UTCOSV refresh
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  30. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-08-31 17:04 UTCOSV refresh
  38. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  41. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  43. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  47. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  51. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  53. 2026-08-14 09:04 UTCEG score recompute
  54. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-08-13 01:03 UTCEG score recompute
  56. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-08-12 00:48 UTCEG score recompute
  58. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-08-11 06:28 UTCEG score recompute
  60. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  61. 2026-08-09 20:58 UTCEG score recompute
  62. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-09 08:41 UTCEG score recompute
  64. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  65. 2026-08-07 20:46 UTCEG score recompute
  66. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  67. 2026-08-06 03:03 UTCEG score recompute
  68. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  69. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  70. 2026-08-04 05:55 UTCEG score recompute
  71. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  72. 2026-08-02 19:37 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27629?
CVE-2026-27629 is a high-severity vulnerability; its CVE record was published on February 25, 2026. InvenTree is an Open Source Inventory Management System. Prior to version 1.2.3, insecure server-side templates can be hijacked to expose secure information to the client. When generating custom batch codes, the InvenTree server makes use of a customizable jinja2 template, which can be modified by…
When was the CVE record for CVE-2026-27629 published?
The CVE record for CVE-2026-27629 was published on February 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-27629 actively exploited?
CVE-2026-27629 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27629?
CVE-2026-27629 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-27629?
The CVE record for CVE-2026-27629 names the fix: "This issue has been addressed in version 1.2.3, and any versions from 1.3.0 onwards."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-27629

Explore →

Is Your Infrastructure Affected by CVE-2026-27629?

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

Book a Demo →Browse All CVEs