Skip to main content
VulnerabilityPublished Updated

CVE-2026-1691: bolo-solo · Deserialization

Affects bolo-soloSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
bolo-soloAffected
  • 2.6.0 – 2.6.4
5 affected builds
Fixed in–
Mavenorg.b3log/bolo-solopkg:maven/org.b3log/bolo-soloOther threatsAffected
  • 2.6.0 – 2.6.4
5 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Administrators should immediately review their bolo-solo deployments to identify affected versions (2.6.0 to 2.6.4). Until an official patch is released, consider the following mitigations: 1) Restrict network access to the bolo-solo service to trusted users and networks only, minimizing exposure to untrusted sources. 2) Implement input validation and sanitization on YAML inputs if possible, or disable importMarkdownsSync functionality if not critical. 3) Use application-layer firewalls or intrusion detection systems to monitor and block suspicious YAML payloads or anomalous requests targeting the vulnerable function. 4) Run bolo-solo with the least privileges necessary to limit the impact of potential exploitation. 5) Monitor security advisories from bolo-solo maintainers for patches and apply them promptly once available. 6) Consider isolating the bolo-solo environment using containerization or sandboxing to contain potential compromise. 7) Conduct regular security audits and penetration tests focusing on deserialization and YAML processing components.

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.

References

Community reviews

Loading reviews…