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

CVE-2026-108641: JeecgBoot Information Disclosure Vulnerability

CVE-2026-108641 is an insecure direct object reference flaw in JeecgBoot that allows authenticated attackers to access other users' private messages. This post explains its impact, affected versions, and mitigation steps.

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-108641 Overview

CVE-2026-108641 is an insecure direct object reference (IDOR) vulnerability in JeecgBoot through version 3.9.5. The flaw resides in the getOne handler of SysAnnouncementSendController, which does not verify that the requesting user owns the delivery record identified by the sendId parameter. Any authenticated low-privilege user can enumerate delivery record identifiers through the unguarded /sys/sysAnnouncementSend/list endpoint and then retrieve message titles, bodies, senders, and recipients belonging to other users. The weakness is tracked as CWE-639: Authorization Bypass Through User-Controlled Key.

Critical Impact

Authenticated attackers can read arbitrary in-application messages across tenants, exposing confidential announcements and recipient metadata.

Affected Products

  • JeecgBoot versions up to and including 3.9.5
  • jeecg-module-system component containing SysAnnouncementSendController
  • Deployments exposing /sys/sysAnnouncementSend/getOne and /sys/sysAnnouncementSend/list endpoints

Discovery Timeline

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

Technical Details for CVE-2026-108641

Vulnerability Analysis

JeecgBoot is a low-code development platform built on Spring Boot. The SysAnnouncementSendController class exposes REST endpoints that manage per-user delivery records for in-application announcements. The getOne handler accepts a sendId request parameter and returns the matching sys_announcement_send record joined with its announcement content. The controller performs no ownership or authorization check against the authenticated principal before returning the row.

Because the sibling /sys/sysAnnouncementSend/list endpoint is reachable by any authenticated user and returns delivery record identifiers without filtering by user_id, an attacker can harvest a complete list of valid sendId values. Each identifier can then be passed back to getOne to retrieve the full announcement payload, including sender, recipient, title, and body. The result is horizontal privilege escalation against the internal messaging feature.

Root Cause

The root cause is missing object-level authorization. The handler at lines 272–276 of SysAnnouncementSendController.java resolves the record directly from the primary key supplied by the client and omits a predicate restricting results to the current session user. See the GitHub source reference for the vulnerable code path.

Attack Vector

Exploitation requires only a valid low-privilege account on the target JeecgBoot instance. The attacker first issues an authenticated GET request to /sys/sysAnnouncementSend/list to enumerate sendId values that belong to other users. The attacker then issues GET /sys/sysAnnouncementSend/getOne?sendId=<id> for each collected identifier and parses the JSON response for titile, msgContent, sender, and userId fields. A public proof of concept is published at the VulnCheck advisory and in the GitHub PoC script.

No verified exploit code is reproduced here. Refer to the linked PoC for request format details.

Detection Methods for CVE-2026-108641

Indicators of Compromise

  • Repeated authenticated requests to /sys/sysAnnouncementSend/getOne with varying sendId values from a single session or source IP.
  • High-volume calls to /sys/sysAnnouncementSend/list followed by sequential getOne requests within short time windows.
  • Access to announcement delivery records where the responding userId field does not match the authenticated principal in session logs.

Detection Strategies

  • Correlate web access logs with session identity to flag getOne responses whose returned recipient does not match the requesting user.
  • Build a baseline of normal getOne request rates per account and alert when a single account exceeds the baseline by an order of magnitude.
  • Hunt for user agents consistent with scripted enumeration, such as python-requests, hitting the sysAnnouncementSend endpoints.

Monitoring Recommendations

  • Forward JeecgBoot application and reverse proxy logs to a centralized SIEM for query-based detection of enumeration patterns.
  • Enable audit logging on the sys_announcement_send table to record read access with the SQL-level user context.
  • Monitor Spring Boot actuator or application metrics for anomalous spikes in SysAnnouncementSendController invocations.

How to Mitigate CVE-2026-108641

Immediate Actions Required

  • Restrict network access to the JeecgBoot management interface so that only trusted users can reach /sys/sysAnnouncementSend/* endpoints.
  • Review application logs for prior enumeration of sendId values and notify affected users if message contents may have been exposed.
  • Rotate any sensitive credentials, tokens, or links that were distributed through in-application announcements.

Patch Information

At the time of publication, no fixed version is identified in the NVD entry. Monitor the JeecgBoot repository and the VulnCheck Security Advisory for an official patched release. Upgrade to a version later than 3.9.5 once the vendor publishes a fix that enforces ownership checks in SysAnnouncementSendController#getOne.

Workarounds

  • Apply a reverse-proxy rule that blocks or requires elevated roles for /sys/sysAnnouncementSend/getOne and /sys/sysAnnouncementSend/list until an upstream patch is available.
  • Add a custom Spring interceptor or @PreAuthorize check that validates the authenticated user owns the requested sendId before invoking the service layer.
  • Disable the in-application messaging feature in environments where it is not required by configuring role permissions to deny access to the announcement send endpoints.
bash
# Example NGINX rule to block the vulnerable endpoint until patched
location ~ ^/sys/sysAnnouncementSend/(getOne|list) {
    return 403;
}

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.