CVE-2026-116339
Received Received - Intake

iFlytek astron-agent DDL Whitelist Bypass

Publication date: 2026-10-26

Last updated on: 2026-10-26

Assigner: VulDB

Description
A vulnerability was determined in iFlytek astron-agent up to 1.1.2. This affects an unknown function of the file core/memory/database/api/v1/exec_ddl.py of the component DDL Whitelist Handler. This manipulation causes incomplete blacklist. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-26
Last Modified
2026-10-26
Generated
2026-10-26
AI Q&A
2026-10-26
EPSS Evaluated
N/A
NVD
CVE-2026-116339
EUVD
EUVD-2026-109940

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
iFlytek astron-agent 1.1.0
iFlytek astron-agent 1.1.1
iFlytek astron-agent 1.1.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-184 The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
CWE-183 The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is in iFlytek astron-agent up to version 1.1.2. It involves a bypass of a Data Definition Language (DDL) whitelist via comment smuggling. The service checks SQL statements for allowlisted keywords but does so by searching the raw SQL string instead of the parsed Abstract Syntax Tree (AST). Attackers can smuggle disallowed commands inside comments, such as /* ALTER TABLE */ CREATE EXTENSION IF NOT EXISTS dblink, which bypasses the whitelist because the keyword is hidden in a comment. The exploit can be initiated remotely without authentication.

Detection Guidance

Check for unauthorized PostgreSQL command execution attempts, especially those using comment smuggling like /* ALTER TABLE */ CREATE EXTENSION. Inspect core-database service logs for rejected DDL statements and look for patterns where commands are hidden in SQL comments. Monitor network traffic for unrecognized database extension installations.

Impact Analysis

An attacker could execute arbitrary PostgreSQL commands with superuser privileges, such as installing malicious extensions like dblink. This could lead to unauthorized database modifications, data theft, or further network compromise. The service lacks authentication, allowing any network peer to interact with it.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. It may result in data breaches, unauthorized modifications, or exposure of protected health information, leading to legal penalties and reputational damage.

Mitigation Strategies

Immediately update astron-agent to the latest version if available. If not, restrict network access to the core-database service to trusted sources only. Implement strict input validation by parsing SQL AST instead of raw strings and stripping comments before whitelist checks. Enable authentication for all database services.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-116339. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart