Skip to main content
Vulnerability Database/CVE-2026-108626

CVE-2026-108626: JeecgBoot Authorization Bypass Vulnerability

CVE-2026-108626 is an authorization bypass vulnerability in JeecgBoot that allows low-privileged users to access message records of other users. This article covers technical details, affected versions, impact, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-108626 Overview

CVE-2026-108626 is a missing authorization vulnerability [CWE-862] affecting JeecgBoot through version 3.9.5. The flaw resides in the SysMessageController.queryById handler, which fails to verify that the authenticated caller owns the requested message record. Any low-privileged authenticated user can issue GET /sys/message/sysMessage/queryById with arbitrary record identifiers and retrieve message push records belonging to other users. Exposed data includes message content and receiver addresses, enabling cross-tenant information disclosure within the low-code platform.

Critical Impact

Authenticated attackers with minimal privileges can enumerate message IDs to disclose message bodies and recipient addresses across the entire JeecgBoot deployment.

Affected Products

  • JeecgBoot low-code development platform through version 3.9.5
  • Deployments exposing the SysMessageController endpoint /sys/message/sysMessage/queryById
  • The jeecg-system-biz module containing the vulnerable handler

Discovery Timeline

  • 2026-10-10 - CVE-2026-108626 published to NVD
  • 2026-10-15 - Last updated in NVD database

Technical Details for CVE-2026-108626

Vulnerability Analysis

The vulnerability is a classic broken object-level authorization flaw in a Spring-based REST controller. The queryById handler in SysMessageController accepts an id query parameter and returns the corresponding SysMessage entity directly from the database. The handler enforces authentication but omits an ownership or role check against the authenticated principal. As a result, any user holding a valid session token can request records belonging to other tenants or administrators.

The disclosed SysMessage records contain the full message body, subject, send status, and receiver address field. In environments where JeecgBoot is used to deliver password resets, notification emails, or workflow messages, this disclosure can expose credentials-in-transit, internal workflows, and personally identifiable information. Because record identifiers are commonly sequential, attackers can enumerate the full message history with a short script.

See the VulnCheck Security Advisory and the vulnerable SysMessageController source lines for details.

Root Cause

The root cause is a missing authorization check [CWE-862] in the queryById method. The handler trusts the client-supplied id and performs a direct lookup without comparing the record's owner or scope against the current user's identity, roles, or tenant.

Attack Vector

An attacker first authenticates to JeecgBoot using any valid low-privileged account, including self-registered users on deployments that allow registration. The attacker then issues GET /sys/message/sysMessage/queryById?id=<record_id> with a numeric or UUID identifier and iterates through the id space. A public proof of concept is available at the GitHub PoC Repository, which automates id enumeration against the endpoint.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-108626

Indicators of Compromise

  • Repeated GET requests to /sys/message/sysMessage/queryById from a single authenticated session, especially with sequential or randomized id values.
  • Access to the queryById endpoint by user accounts that have no legitimate messaging-administration role.
  • Spikes in SysMessage read volume disproportionate to the user population.

Detection Strategies

  • Deploy application-layer logging that captures the authenticated user, source IP, and requested id for every call to /sys/message/sysMessage/queryById.
  • Correlate authenticated session identifiers with the number of distinct SysMessage ids retrieved per hour and alert on outliers.
  • Add web application firewall rules that rate-limit requests to the queryById endpoint per session token.

Monitoring Recommendations

  • Review historical access logs for the /sys/message/sysMessage/queryById path dating back to the first deployment of JeecgBoot 3.9.5 or earlier.
  • Monitor outbound email, SMS, and notification channels for recipient addresses that match disclosed records to identify downstream phishing follow-up.
  • Track creation of new low-privileged accounts followed within minutes by access to messaging endpoints.

How to Mitigate CVE-2026-108626

Immediate Actions Required

  • Restrict network access to the JeecgBoot administrative API, placing /sys/message/* endpoints behind an internal network or VPN where feasible.
  • Disable self-registration on JeecgBoot deployments to raise the barrier for obtaining the authenticated session required for exploitation.
  • Audit the SysMessage table for records containing credentials, reset tokens, or sensitive personal data and rotate any exposed secrets.

Patch Information

No fixed JeecgBoot release is identified in the NVD entry at the time of publication. The vulnerability affects JeecgBoot through 3.9.5. Monitor the JeecgBoot repository and the VulnCheck Security Advisory for the official patched version and upgrade as soon as it is published.

Workarounds

  • Apply an authorization filter or Spring HandlerInterceptor that rejects requests to queryById unless the authenticated user owns the record or holds a messaging-administrator role.
  • Add a reverse-proxy allow-list that restricts /sys/message/sysMessage/queryById to specific administrator source IPs until a vendor patch is applied.
  • Replace sequential numeric identifiers in SysMessage with unguessable UUIDs to reduce enumeration efficiency as a defense-in-depth control.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.