CVE-2026-68503: LazyOwn: Default C2 Operator Credentials Enable Administrative Access to C2 Dashboard

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-07-30).

Weakness: CWE-1392: Use of Default Credentials

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 5 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 7 references on Exploit Observer

Live scores

EPSS
0.008
low predicted chance of attack
VEDAS
0.988
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei · Suricata

Who is affected

ProductAffectedNot affected
grisuno LazyOwnversion < 0.2.154Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

LazyOwn - Default Credentials

LazyOwn RedTeam/APT Framework before 0.2.154 ships default C2 credentials (LazyOwn / LazyOwn) in payload.json and passes them unchanged to the lazyc2.py HTTP Basic authentication gate. Any network-reachable unauthenticated attacker who knows the defaults can authenticate to the C2 dashboard with operator-level access. The template sends an unauthenticated request (expecting the Basic-auth rejection) and then the same request with the default credentials, confirming the gate is defeated.

Name and description quoted from the template, written by VEDAS.

The template sends 2 requests (GET /api/data, GET /api/data); it decides using dsl matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-68503.yaml
Show the template (44 lines)
yaml
id: CVE-2026-68503

info:
  name: "LazyOwn - Default Credentials"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    LazyOwn RedTeam/APT Framework before 0.2.154 ships default C2 credentials (LazyOwn / LazyOwn)
    in payload.json and passes them unchanged to the lazyc2.py HTTP Basic authentication gate. Any
    network-reachable unauthenticated attacker who knows the defaults can authenticate to the C2
    dashboard with operator-level access. The template sends an unauthenticated request (expecting
    the Basic-auth rejection) and then the same request with the default credentials, confirming the
    gate is defeated.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-68503&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=lazyown&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2026-68503
    cwe-id: CWE-1392
  metadata:
    verified: false
    max-request: 2
  tags: cve,cve2026,lazyown,default-login,auth-bypass
http:
  - raw:
      - |
        GET /api/data HTTP/1.1
        Host: {{Hostname}}
      - |
        GET /api/data HTTP/1.1
        Host: {{Hostname}}
        Authorization: Basic TGF6eU93bjpMYXp5T3du

    req-condition: true
    matchers:
      - type: dsl
        dsl:
          - 'status_code_1 == 401'
          - 'contains(body_1, "Invalid credentials. Please provide valid username")'
          - 'status_code_2 != 401'
          - '!contains(body_2, "Invalid credentials. Please provide valid username")'
        condition: and

CVE-2026-68503.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-68503 LazyOwn - Default Credentials. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-68503 LazyOwn - Default Credentials"; flow:established,to_server; http.header; content:"Basic TGF6eU93bjpMYXp5T3du"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-68503; reference:url,https://www.exploit.observer/?keyword=CVE-2026-68503&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=lazyown&match=exact; sid:1086401; rev:1;)

CVE-2026-68503.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust