CVE-2026-2623: A flaw has been found in Blossom up to 1.17.1

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

blossom: upgrade to newer than 1.17.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-2623 being exploited?

CVE-2026-2623 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-2623 affect?

CVE-2026-2623 affects blossom. Severity is medium (CVSS 6.3). A flaw has been found in Blossom up to 1.17.1. This issue affects the function put of the file blossom-backend/common/common-iaas/src/main/java/com/blossom/common/iaas/blos/BLOSManager.java of the component File Upload. This manipulation ca

Q: How urgent is CVE-2026-2623?

Priority 40/100. Public exploit reference

This month

MEDIUM 6.3UPGRADE

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

A flaw has been found in Blossom up to 1.17.1. This issue affects the function put of the file blossom-backend/common/common-iaas/src/main/java/com/blossom/common/iaas/blos/BLOSManager.java of the component File Upload. This manipulation causes path traversal. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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.7% (top 47%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-02-17
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: wangyunf

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

Am I affected?

Timeline

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

wangyunf blossom UPGRADE

Affected: <= 1.17.1

Fixed in: newer than 1.17.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy blossom || rpm -q blossom || blossom --version

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

sudo apt update && sudo apt install --only-upgrade blossom

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade blossom

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-2623?

blossom: upgrade to newer than 1.17.1. Exact commands for each OS are on this page.

Is CVE-2026-2623 being exploited?

CVE-2026-2623 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-2623 affect?

CVE-2026-2623 affects blossom. Severity is medium (CVSS 6.3). A flaw has been found in Blossom up to 1.17.1. This issue affects the function put of the file blossom-backend/common/common-iaas/src/main/java/com/blossom/common/iaas/blos/BLOSManager.java of the component File Upload. This manipulation ca

How urgent is CVE-2026-2623?

Priority 40/100. Public exploit reference

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-2622 LOW 3.5 UPGRADE A vulnerability was detected in Blossom up to 1.17.1

References

← Back to latest CVEs