CVE-2026-1691
Unknown Unknown - Not Provided
Remote Deserialization Vulnerability in bolo-solo SnakeYAML Component

Publication date: 2026-01-30

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability has been found in bolo-solo up to 2.6.4. This impacts the function importMarkdownsSync of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component SnakeYAML. Such manipulation leads to deserialization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-30
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-01-30
EPSS Evaluated
2026-06-14
NVD
CVE-2026-1691
EUVD
EUVD-2026-5013
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
adlered bolo-solo to 2.6.4 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-1691 is a deserialization vulnerability in bolo-solo up to version 2.6.4, specifically in the importMarkdownsSync function of BackupService.java. The vulnerability arises because the application uses the SnakeYAML library to deserialize YAML content from user-uploaded markdown files without secure loading or validation. This allows an attacker to craft malicious YAML payloads that, when processed, lead to arbitrary code execution on the server remotely. The exploit involves uploading a markdown file containing a malicious YAML payload that triggers unsafe deserialization, enabling execution of attacker-controlled code. [1, 2, 3]

Impact Analysis

This vulnerability can allow a remote attacker to execute arbitrary code on the affected server without authentication. By exploiting the insecure YAML deserialization, an attacker can gain full control over the target system, potentially compromising confidentiality, integrity, and availability of the system and its data. This could lead to unauthorized access, data breaches, service disruption, or further attacks launched from the compromised server. [1, 2, 3]

Detection Guidance

Detection can involve monitoring for uploads of malicious markdown files containing crafted YAML payloads to the /import/markdown interface of bolo-solo. Since the vulnerability is exploited by uploading specially crafted markdown files that trigger unsafe deserialization, inspecting logs for such uploads or scanning for unusual activity related to the importMarkdownsSync function may help. However, no specific detection commands are provided in the resources. [1, 2, 3]

Mitigation Strategies

Immediate mitigation steps include preventing the upload of untrusted markdown files to the /import/markdown interface, disabling or restricting the importMarkdownsSync functionality, and avoiding use of the vulnerable bolo-solo versions (up to 2.6.4). Since no known countermeasures or mitigations currently exist, replacing or patching the affected component (SnakeYAML usage in BackupService.java) to use secure YAML loading practices is recommended. Monitoring for updates or patches from the vendor is also advised. [3, 1, 2]

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