CVE-2026-15506

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-13. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

A security vulnerability has been detected in SecureAge CatchPulse up to 10.9.3. The affected element is an unknown function in the library saappctl.sys of the component Driver. Such manipulation leads to heap-based buffer overflow. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. Upgrading to version 10.10.0 is sufficient to fix this issue. You should upgrade the affected component. The vendor was contacted early about this disclosure.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
51(Track*)
EG Risk 51/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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
3.9%
KEV
Not listed

Published

July 12, 2026

Last Modified

July 14, 2026

Advisory Details (1)

Auto-updated Jul 12, 2026
No patch confirmed yet.
generic
https://youtu.be/xZqRVWlrah8

Vendor Advisories for CVE-2026-15506(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 9× in last 7d / 29× 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-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:05 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-17 04:45 UTCGHSA enrichment
  11. 2026-07-16 17:21 UTCGHSA enrichment
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-16 05:54 UTCGHSA enrichment
  14. 2026-07-15 18:29 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 07:02 UTCGHSA enrichment
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 19:37 UTCGHSA enrichment
  19. 2026-07-14 17:20 UTCNVD updateCVSS v4 → 7.1
  20. 2026-07-14 16:40 UTCMITRE cvelistV5CVSS v4 → 8.5
  21. 2026-07-14 08:08 UTCGHSA enrichment
  22. 2026-07-13 22:30 UTCEPSS rescore
  23. 2026-07-13 20:43 UTCGHSA enrichment
  24. 2026-07-13 20:08 UTCNVD updateCVSS v4 → 7.1
  25. 2026-07-13 18:27 UTCMITRE cvelistV5CVSS v4 → 8.5
Show 4 more
  1. 2026-07-13 09:17 UTCGHSA enrichment
  2. 2026-07-12 22:17 UTCNVD updateCVSS v4 → 7.1
  3. 2026-07-12 21:53 UTCEG score recompute
  4. 2026-07-12 21:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15506?
CVE-2026-15506 is a high vulnerability published on July 12, 2026. A security vulnerability has been detected in SecureAge CatchPulse up to 10.9.3. The affected element is an unknown function in the library saappctl.sys of the component Driver. Such manipulation leads to heap-based buffer overflow. An attack has to be approached locally. The exploit has been…
When was CVE-2026-15506 disclosed?
CVE-2026-15506 was first published in the National Vulnerability Database on July 12, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15506 actively exploited?
CVE-2026-15506 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15506?
CVE-2026-15506 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-15506?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15506, 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-15506

Explore →

Is Your Infrastructure Affected by CVE-2026-15506?

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

Start Free Scan →Browse All CVEs