CVE-2025-14103

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-02-25. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.7 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an unauthorized user with Developer-role permissions to set pipeline variables for manually triggered jobs under certain conditions.

CVSS v3
4.3
EG Score
4.3(medium)
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 computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

February 25, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

GitLab Patch Release: 18.9.1, 18.8.5, 18.7.5 | GitLab Docs

https://about.gitlab.com/releases/2026/02/25/patch-release-gitlab-18-9-1-released/

Vendor Advisories for CVE-2025-14103(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 7× in last 7d / 27× 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.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-18 19:20 UTCOSV refresh
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-16 05:13 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-13 16:45 UTCEPSS rescore
  7. 2026-09-12 14:59 UTCEPSS rescore
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-10 09:33 UTCEPSS rescore
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-04 13:59 UTCEPSS rescore
  15. 2026-09-04 05:05 UTCEPSS rescore
  16. 2026-09-02 14:10 UTCEPSS rescore
  17. 2026-09-01 13:52 UTCEPSS rescore
  18. 2026-08-30 22:47 UTCOSV refresh
  19. 2026-08-30 19:16 UTCEPSS rescore
  20. 2026-08-30 01:21 UTCEPSS rescore
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 14:45 UTCEPSS rescore
  24. 2026-08-25 13:47 UTCEPSS rescore
  25. 2026-08-24 14:15 UTCEPSS rescore
Show 46 more
  1. 2026-08-21 23:48 UTCEPSS rescore
  2. 2026-08-20 22:54 UTCEPSS rescore
  3. 2026-08-19 17:02 UTCEPSS rescore
  4. 2026-08-18 13:47 UTCEPSS rescore
  5. 2026-08-17 13:46 UTCEPSS rescore
  6. 2026-08-16 14:55 UTCEPSS rescore
  7. 2026-08-16 02:13 UTCEPSS rescore
  8. 2026-08-16 02:13 UTCEPSS rescore
  9. 2026-08-15 01:29 UTCEPSS rescore
  10. 2026-08-14 09:00 UTCEG score recompute
  11. 2026-08-14 09:00 UTCGHSA enrichment
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-13 01:00 UTCEG score recompute
  14. 2026-08-13 01:00 UTCGHSA enrichment
  15. 2026-08-12 13:49 UTCEPSS rescore
  16. 2026-08-11 13:41 UTCEPSS rescore
  17. 2026-08-11 07:00 UTCEG score recompute
  18. 2026-08-11 07:00 UTCGHSA enrichment
  19. 2026-08-10 23:59 UTCEPSS rescore
  20. 2026-08-10 08:46 UTCEG score recompute
  21. 2026-08-10 08:46 UTCGHSA enrichment
  22. 2026-08-09 13:45 UTCEPSS rescore
  23. 2026-08-09 08:38 UTCEG score recompute
  24. 2026-08-09 08:38 UTCGHSA enrichment
  25. 2026-08-07 20:42 UTCEG score recompute
  26. 2026-08-07 20:42 UTCGHSA enrichment
  27. 2026-08-07 16:26 UTCEPSS rescore
  28. 2026-08-06 13:45 UTCEPSS rescore
  29. 2026-08-06 03:00 UTCEG score recompute
  30. 2026-08-06 03:00 UTCGHSA enrichment
  31. 2026-08-05 19:16 UTCEPSS rescore
  32. 2026-08-04 15:09 UTCEPSS rescore
  33. 2026-08-04 10:37 UTCEPSS rescore
  34. 2026-08-04 05:50 UTCEG score recompute
  35. 2026-08-04 05:50 UTCGHSA enrichment
  36. 2026-08-03 10:35 UTCEPSS rescore
  37. 2026-08-02 19:33 UTCEG score recompute
  38. 2026-08-02 19:33 UTCGHSA enrichment
  39. 2026-08-02 02:25 UTCEPSS rescore
  40. 2026-08-01 04:14 UTCEPSS rescore
  41. 2026-07-30 16:26 UTCEPSS rescore
  42. 2026-07-30 01:29 UTCEPSS rescore
  43. 2026-07-28 15:35 UTCEPSS rescore
  44. 2026-07-27 14:12 UTCEPSS rescore
  45. 2026-07-27 12:55 UTCEG score recompute
  46. 2026-07-27 12:55 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-14103?
CVE-2025-14103 is a medium vulnerability published on February 25, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.7 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an unauthorized user with Developer-role permissions to set pipeline variables for manually triggered jobs under certain conditions.
When was CVE-2025-14103 disclosed?
CVE-2025-14103 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-14103 actively exploited?
CVE-2025-14103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.1% of all scored CVEs.
What is the CVSS score of CVE-2025-14103?
CVE-2025-14103 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2025-14103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-14103, 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

Explore the affected products and dependency analysis for CVE-2025-14103

Explore →

Is Your Infrastructure Affected by CVE-2025-14103?

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

Start Free Scan →Browse All CVEs