A flaw has been found in H3C SecPath F1000-C8300 up to 20260522. This impacts an unknown function of the file /webui/?g=log_fw_nbc_mail_jsondata. Executing a manipulation of the argument subject can lead to sql injection. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure and confirmed the existence of the vulnerability. A technical fix is planned to be released.
CVE-2026-15907
Score 7.3 from GitHub Security Advisory published 2026-07-16. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EG Risk
- 64(Attend)EG Risk 64/100SSVC: Attend
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 computedSeverity73% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 16, 2026
References (5)
Vendor Advisories for CVE-2026-15907(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× 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.
- 2026-07-27 22:53 UTCEG score recompute
- 2026-07-27 22:53 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 10:49 UTCGHSA enrichment
- 2026-07-26 23:08 UTCEG score recompute
- 2026-07-26 23:08 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 11:28 UTCEG score recompute
- 2026-07-26 11:28 UTCGHSA enrichment
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 23:25 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 16:30 UTCNVD updateCVSS v4 → 5.5
- 2026-07-16 15:23 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-07-16 11:45 UTCGHSA enrichment
- 2026-07-16 00:25 UTCNVD updateCVSS v4 → 5.5
Show 2 moreShow fewer
- 2026-07-16 00:05 UTCEG score recompute
- 2026-07-16 00:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-15907?
When was CVE-2026-15907 disclosed?
Is CVE-2026-15907 actively exploited?
What is the CVSS score of CVE-2026-15907?
How do I remediate CVE-2026-15907?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15907
Is Your Infrastructure Affected by CVE-2026-15907?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.