Skip to main content
VulnerabilityPublished Updated

CVE-2026-1810: bolo-solo · Path Traversal

Affects bolo-soloSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% 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 3 Feb 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-blogbolo-soloAffected
  • 2.6.0 – 2.6.4
5 affected builds
Fixed in–
GitHubbolo-blog/bolo-solopkg:github/bolo-blog/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

To mitigate CVE-2026-1810, organizations should first implement strict input validation and sanitization on any ZIP file uploads or processing, ensuring that file paths do not contain directory traversal sequences such as '../'. Employ whitelisting of allowed file paths and enforce extraction only within designated directories using secure APIs that prevent path traversal. If possible, restrict ZIP file handling to trusted users or isolate the processing environment using containerization or sandboxing to limit potential damage. Monitor logs for suspicious ZIP file upload activity or unusual file system changes. Additionally, restrict permissions on directories used for ZIP extraction to minimize impact if exploitation occurs. Regularly back up critical data and maintain an incident response plan to quickly address potential exploitation. Stay alert for vendor updates or community patches and apply them promptly once available.

Description

A vulnerability was detected in bolo-blog bolo-solo up to 2.6.4. The impacted element is the function unpackFilteredZip of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component ZIP File Handler. Performing a manipulation of the argument File results in path traversal. The attack is possible to be carried out remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

References

Community reviews

Loading reviews…