CVE-2026-68503

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

LazyOwn RedTeam/APT Framework is an AI-powered C2 and red-team operations framework. Prior to 0.2.154, LazyOwn ships default C2 credentials LazyOwn and LazyOwn in payload.json and core/payload_schema.py and passes them unchanged to lazyc2.py HTTP Basic authentication, allowing any network-reachable attacker who knows the defaults to authenticate to the C2 dashboard with operator-level access. This issue is fixed in 0.2.154.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/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 computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 30, 2026

Last Modified

July 31, 2026

Advisory Details (2)

Auto-updated Aug 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Default C2 Operator Credentials Enable Administrative Access to C2 Dashboard · Advisory · grisuno/LazyOwn · GitHub

https://github.com/grisuno/LazyOwn/security/advisories/GHSA-38jf-j9x7-jf6f
github_commit

commit 2e1e3a7b5da8 (grisuno/LazyOwn)

Fix landed in grisuno/LazyOwn commit 2e1e3a7b5da8 — awaiting tagged release

https://github.com/grisuno/LazyOwn/commit/2e1e3a7b5da8149ae28a970b5883aefa42921652

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 55× 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-08-25 13:51 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 15:57 UTCEG score recompute
  4. 2026-08-24 12:19 UTCEG score recompute
  5. 2026-08-23 03:49 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 02:30 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 01:13 UTCEG score recompute
  10. 2026-08-20 22:56 UTCEPSS rescore
  11. 2026-08-19 19:28 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 15:52 UTCEG score recompute
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-17 15:23 UTCEG score recompute
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 17:42 UTCEG score recompute
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 03:16 UTCEG score recompute
  22. 2026-08-15 01:57 UTCEG score recompute
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 00:42 UTCEG score recompute
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 30 more
  1. 2026-08-12 16:04 UTCEG score recompute
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-11 14:46 UTCEG score recompute
  4. 2026-08-11 00:19 UTCEG score recompute
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-09 15:49 UTCEG score recompute
  7. 2026-08-09 13:47 UTCEPSS rescore
  8. 2026-08-08 18:10 UTCEG score recompute
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-07 16:53 UTCEG score recompute
  11. 2026-08-06 15:30 UTCEG score recompute
  12. 2026-08-06 13:47 UTCEPSS rescore
  13. 2026-08-05 21:25 UTCEG score recompute
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 16:04 UTCEG score recompute
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 12:27 UTCEG score recompute
  19. 2026-08-04 10:39 UTCEPSS rescore
  20. 2026-08-03 13:12 UTCEG score recompute
  21. 2026-08-03 10:36 UTCEPSS rescore
  22. 2026-08-02 04:40 UTCEG score recompute
  23. 2026-08-02 02:27 UTCEPSS rescore
  24. 2026-08-01 06:56 UTCEG score recompute
  25. 2026-08-01 04:16 UTCEPSS rescore
  26. 2026-07-31 20:02 UTCEG score recompute
  27. 2026-07-31 16:25 UTCEG score recompute
  28. 2026-07-30 21:36 UTCEG score recompute
  29. 2026-07-30 21:02 UTCEG score recompute
  30. 2026-07-30 21:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68503?
CVE-2026-68503 is a critical vulnerability published on July 30, 2026. LazyOwn RedTeam/APT Framework is an AI-powered C2 and red-team operations framework. Prior to 0.2.154, LazyOwn ships default C2 credentials LazyOwn and LazyOwn in payload.json and core/payload_schema.py and passes them unchanged to lazyc2.py HTTP Basic authentication, allowing any network-reachable…
When was CVE-2026-68503 disclosed?
CVE-2026-68503 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68503 actively exploited?
CVE-2026-68503 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 67.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68503?
CVE-2026-68503 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-68503?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68503, 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-68503

Explore →

Is Your Infrastructure Affected by CVE-2026-68503?

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

Start Free Scan →Browse All CVEs