CVE-2026-1811: A flaw has been found in bolo-blog bolo-solo up to 2.6.4

Q: How do I fix CVE-2026-1811?

bolo-solo: upgrade to newer than 2.6.4. Exact commands for each OS are on this page.

Q: Is CVE-2026-1811 being exploited?

CVE-2026-1811 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-1811 affect?

CVE-2026-1811 affects bolo-solo. Severity is medium (CVSS 6.3). A flaw has been found in bolo-blog bolo-solo up to 2.6.4. This affects the function importFromMarkdown of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component Filename Handler. Executing a manipulation of the

Q: How urgent is CVE-2026-1811?

Priority 38/100. Public exploit reference

Routine

MEDIUM 6.3UPGRADE

CVE-2026-1811 is a medium-severity flaw (CVSS 6.3) affecting bolo-solo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A flaw has been found in bolo-blog bolo-solo up to 2.6.4. This affects the function importFromMarkdown of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component Filename Handler. Executing a manipulation of the argument File can lead to path traversal. The attack may be performed from remote. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has n

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-02-03
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: adlered

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-03 22:16 UTCPublished CVE record published
2026-06-17 10:16 UTCUpdated Record last modified

adlered bolo-solo UPGRADE

Affected: <= 2.6.4

Fixed in: newer than 2.6.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy bolo-solo || rpm -q bolo-solo || bolo-solo --version

2. UPGRADE to newer than 2.6.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bolo-solo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bolo-solo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-1811?

bolo-solo: upgrade to newer than 2.6.4. Exact commands for each OS are on this page.

Is CVE-2026-1811 being exploited?

CVE-2026-1811 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-1811 affect?

CVE-2026-1811 affects bolo-solo. Severity is medium (CVSS 6.3). A flaw has been found in bolo-blog bolo-solo up to 2.6.4. This affects the function importFromMarkdown of the file src/main/java/org/b3log/solo/bolo/prop/BackupService.java of the component Filename Handler. Executing a manipulation of the

How urgent is CVE-2026-1811?

Priority 38/100. Public exploit reference

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-1813 MEDIUM 6.3 UPGRADE A vulnerability was found in bolo-blog bolo-solo up to 2.6.4
CVE-2026-1812 MEDIUM 6.3 UPGRADE A vulnerability has been found in bolo-blog bolo-solo up to 2.6.4
CVE-2026-1810 MEDIUM 6.3 UPGRADE A vulnerability was detected in bolo-blog bolo-solo up to 2.6.4

References

← Back to latest CVEs