CVE-2026-25825

LOWPre-NVD 2.72.7—
EchelonGraph scoreHIGH confidence

Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-09-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 2.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: None knownExposed: 0

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

An issue was discovered in Keyfactor SignServer before 7.6.0. The output file to which SignerStatusReportWorker logs the report can be set to any path, even one that points to a file that already exists. This gives a user (with admin access) the possibility to write files in arbitrary directories in the server filesystem and potentially overwrite files accessible by the local user JBoss.

CVSS v3
2.7
EG Score
2.7(high)
EG Risk
12(Track)
EG Risk 12/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
Severity27% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 22, 2026

References (2)

Vendor Advisories for CVE-2026-25825(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 10× in last 7d / 17× 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-24 14:03 UTCEPSS rescore
  2. 2026-09-22 20:13 UTCEG score recompute
  3. 2026-09-22 20:13 UTCGHSA enrichment
  4. 2026-09-22 16:26 UTCGHSA enrichment
  5. 2026-09-22 15:30 UTCEG score recompute▲ 2.70
  6. 2026-09-22 15:30 UTCGHSA enrichment
  7. 2026-09-22 15:29 UTCMITRE cvelistV5CVSS v3 → 2.7 · severity → LOW
  8. 2026-09-21 04:55 UTCGHSA enrichment
  9. 2026-09-20 20:15 UTCEPSS rescore
  10. 2026-09-18 19:27 UTCEPSS rescore
  11. 2026-09-18 10:14 UTCEG score recompute
  12. 2026-09-18 10:14 UTCGHSA enrichment
  13. 2026-09-16 14:07 UTCEPSS rescore
  14. 2026-09-15 15:32 UTCGHSA enrichment
  15. 2026-09-15 15:31 UTCNVD update
  16. 2026-09-15 14:33 UTCEG score recompute
  17. 2026-09-15 14:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-25825?
CVE-2026-25825 is a low vulnerability published on September 15, 2026. An issue was discovered in Keyfactor SignServer before 7.6.0. The output file to which SignerStatusReportWorker logs the report can be set to any path, even one that points to a file that already exists. This gives a user (with admin access) the possibility to write files in arbitrary directories…
When was CVE-2026-25825 disclosed?
CVE-2026-25825 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25825 actively exploited?
CVE-2026-25825 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 80.6% of all scored CVEs.
What is the CVSS score of CVE-2026-25825?
CVE-2026-25825 has a CVSS v3.1 base score of 2.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-25825?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25825, 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-2026-25825

Explore →

Is Your Infrastructure Affected by CVE-2026-25825?

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

Book a Demo →Browse All CVEs