Skip to main content
VulnerabilityPublished Updated

CVE-2026-8890: code100x · Insecure Direct Object Reference

Affects code100xSource CVE Database V5

0
Compare

Public exploit available · CVSS 8.2 High.

Data as of 8 Nov 2026, 14:21 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 3.18.2
CNA (VulnCheck)CVSS 4.08.8
CISA SSVC
Exploitation
Proof of concept is public or traded
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-05-26.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 26 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulnCheck

    , 8 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 1 hour after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
code100xcode100xAffected
  • =0
Fixed in–

AI-suggested

Users of code100x version 0 should implement additional access controls or input validation as a temporary mitigation. Monitor vendor advisories for updates and apply official patches once released.

Description

code100x version 0 contains an authentication bypass vulnerability in its Mobile API. An attacker can impersonate arbitrary users by sending a crafted JSON payload in the 'g' HTTP header. The middleware fails to validate the 'Auth-Key' header value, allowing spoofing of user identity headers that downstream handlers trust, leading to unauthorized access to course data of any enrolled user or administrator.

References

Community reviews

Loading reviews…