CVE-2026-108657

waiting for further signalsZero needs more public information before it can validate it.

GHSA-gp9m-m3c8-jw96 ↗EUVD-2026-96596 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
JeecgBoot <= 3.9.5
ETK-2026-1203Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 22h 33msince last run
1h 26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+129h22m
0
+2h
+4h
+6h
+8h
+10h

description

JeecgBoot versions through 3.9.5 do not properly enforce authorization for tenant application approvals. An attacker with an authenticated account can improperly grant tenant administrator permissions; a valid user session is required.

mitigation

Restrict or disable tenant application approval functionality, including access to the affected approval endpoint, until a patched release is available. Limit access to trusted administrative networks and accounts as an interim control.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%13th percentile
agent run time
1h 26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 21:49Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-10 21:49Z
    ghsa: trigger signal, started the run
  2. 2026-10-10 21:49Z

this entry in the feed

GET /api/v1/feed/CVE-2026-108657

{
  "etk_id": "ETK-2026-1203",
  "cve_id": "CVE-2026-108657",
  "display_id": "CVE-2026-108657",
  "ghsa_id": "GHSA-gp9m-m3c8-jw96",
  "euvd_id": "EUVD-2026-96596",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in JeecgBoot tenant approval",
  "summary": "JeecgBoot versions through 3.9.5 do not properly enforce authorization for tenant application approvals. An attacker with an authenticated account can improperly grant tenant administrator permissions; a valid user session is required.",
  "mitigation": "Restrict or disable tenant application approval functionality, including access to the affected approval endpoint, until a patched release is available. Limit access to trusted administrative networks and accounts as an interim control.",
  "vendor": "jeecgboot",
  "product": "JeecgBoot",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.9.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "JeecgBoot",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1304,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 86.08332593333333,
  "t0_at": "2026-10-10T21:49:43.999000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T21:49:43.999000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T21:49:43.999000+00:00",
      "url": "https://github.com/advisories/GHSA-gp9m-m3c8-jw96"
    }
  }
}

published 2026-10-11 02:26Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.