CVE-2026-68503

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Oct 9, 2026
Fix named in the CVE record. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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 / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 130 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  2. 2026-10-12 15:45 UTCEG score recompute
  3. 2026-10-11 19:30 UTCEG score recompute
  4. 2026-10-11 16:45 UTCEG score recompute
  5. 2026-10-11 14:06 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  11. 2026-10-06 23:52 UTCEG score recompute
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  13. 2026-10-05 19:59 UTCEG score recompute
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  15. 2026-10-04 23:55 UTCEG score recompute
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  17. 2026-10-04 06:36 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  19. 2026-10-03 02:48 UTCEG score recompute
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  21. 2026-10-02 16:55 UTCEG score recompute
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  23. 2026-10-01 02:51 UTCEG score recompute
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  25. 2026-09-29 06:52 UTCEG score recompute
Show 73 more
  1. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  2. 2026-09-27 18:58 UTCEG score recompute
  3. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  5. 2026-09-25 04:55 UTCEG score recompute
  6. 2026-09-23 21:28 UTCEG score recompute
  7. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-09-22 21:35 UTCEG score recompute
  9. 2026-09-22 15:11 UTCEG score recompute
  10. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-09-20 21:15 UTCEG score recompute
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-09-19 23:46 UTCEG score recompute
  14. 2026-09-18 22:25 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-09-18 01:18 UTCEG score recompute
  17. 2026-09-17 01:28 UTCEG score recompute
  18. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-09-16 05:32 UTCEG score recompute
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-09-15 03:13 UTCEG score recompute
  22. 2026-09-13 18:13 UTCEG score recompute
  23. 2026-09-12 16:03 UTCEG score recompute
  24. 2026-09-11 14:59 UTCEG score recompute
  25. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  27. 2026-09-10 12:57 UTCEG score recompute
  28. 2026-09-09 07:10 UTCEG score recompute
  29. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  30. 2026-09-07 19:45 UTCEG score recompute
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  32. 2026-09-06 16:41 UTCEG score recompute
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  34. 2026-09-05 18:49 UTCEG score recompute
  35. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  36. 2026-09-04 15:12 UTCEG score recompute
  37. 2026-09-04 11:26 UTCEG score recompute
  38. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  39. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  40. 2026-09-01 22:36 UTCEG score recompute
  41. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  42. 2026-09-01 07:27 UTCEG score recompute
  43. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  44. 2026-08-30 21:16 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  46. 2026-08-30 02:06 UTCEG score recompute
  47. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  48. 2026-08-29 22:29 UTCEG score recompute
  49. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-08-27 20:47 UTCEG score recompute
  51. 2026-08-26 15:23 UTCEG score recompute
  52. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  53. 2026-08-25 13:51 UTCEG score recompute
  54. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  55. 2026-08-24 15:57 UTCEG score recompute
  56. 2026-08-24 12:19 UTCEG score recompute
  57. 2026-08-23 03:49 UTCEG score recompute
  58. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  59. 2026-08-22 02:30 UTCEG score recompute
  60. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  61. 2026-08-21 01:13 UTCEG score recompute
  62. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  63. 2026-08-19 19:28 UTCEG score recompute
  64. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  65. 2026-08-18 15:52 UTCEG score recompute
  66. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-08-17 15:23 UTCEG score recompute
  68. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  69. 2026-08-16 17:42 UTCEG score recompute
  70. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  71. 2026-08-16 03:16 UTCEG score recompute
  72. 2026-08-15 01:57 UTCEG score recompute
  73. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-68503?
CVE-2026-68503 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-68503 published?
The CVE record for CVE-2026-68503 was published on July 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-68503 actively exploited?
CVE-2026-68503 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68503?
CVE-2026-68503 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68503?
The CVE record for CVE-2026-68503 names the fix: "This issue is fixed in 0.2.154."

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.

Book a Demo →Browse All CVEs