Overview 9 matches · 2 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
9matches
2in Waratek scope22.2%
2protected22.2%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
2
22.2%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
7
77.8%
Withdrawn CVE
0
0.0%
blocked by ARMR today
2
22.2%
partly blocked
0
0.0%
not blocked
7
77.8%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
2
22.2%
Forecast only
0
0.0%
No public exploit
7
77.8%
split by
peak 2 / year
20181
Not applicable1
Medium1
not blocked1
No public exploit1
20190
20202
Not applicable2
Medium2
not blocked2
No public exploit2
20212
Not applicable2
Medium2
not blocked2
No public exploit2
20220
20230
20241
Not applicable1
Medium1
not blocked1
No public exploit1
20251
Not applicable1
Medium1
not blocked1
No public exploit1
20262
Protected by Waratek2
Medium2
blocked by ARMR today2
Proof of concept only2
201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-22187 | Medium | 2026-01-07 | Protected by Waratek | Proof of concept only | Bio-Formats versions up to and including 8.3.0 perform unsafe Java deserialization of attacker-controlled memoization cache files (.bfmemo) during image processing. The loci.formats.Memoizer class automatically loads and deserializes memo files associated with images without validation, integrity checks, or trust enforcement. An attacker who can supply a crafted .bfmemo file alongside an image can trigger deserialization of untrusted data, which may result in denial of service, logic manipulation, or potentially remote code execution in environments where suitable gadget chains are present on the classpath. |
| CVE-2026-22186 | Medium | 2026-01-07 | Protected by Waratek | Proof of concept only | Bio-Formats versions up to and including 8.3.0 contain an XML External Entity (XXE) vulnerability in the Leica Microsystems metadata parsing component (e.g., XLEF). The parser uses an insecurely configured DocumentBuilderFactory when processing Leica XML-based metadata files, allowing external entity expansion and external DTD loading. A crafted metadata file can trigger outbound network requests (SSRF), access local system resources where readable, or cause a denial of service during XML parsing. |
| CVE-2025-54791 | Medium | 2025-08-13 | Not applicable | No public exploit | OMERO.web provides a web based client and plugin infrastructure. Prior to version 5.29.2, if an error occurred when resetting a user's password using the Forgot Password option in OMERO.web, the error message displayed on the Web page can disclose information about the user. This issue has been patched in version 5.29.2. A workaround involves disabling the Forgot password option in OMERO.web using the omero.web.show_forgot_password configuration property. |
| CVE-2024-35180 | Medium | 2024-05-21 | Not applicable | No public exploit | OMERO.web provides a web based client and plugin infrastructure. There is currently no escaping or validation of the `callback` parameter that can be passed to various OMERO.web endpoints that have JSONP enabled. This vulnerability has been patched in version 5.26.0. |
| CVE-2021-21377 | Medium | 2021-03-23 | Not applicable | No public exploit | OMERO.web is open source Django-based software for managing microscopy imaging. OMERO.web before version 5.9.0 supports redirection to a given URL after performing login or switching the group context. These URLs are not validated, allowing redirection to untrusted sites. OMERO.web 5.9.0 adds URL validation before redirecting. External URLs are not considered valid, unless specified in the omero.web.redirect_allowed_hosts setting. |
| CVE-2021-21376 | Medium | 2021-03-23 | Not applicable | No public exploit | OMERO.web is open source Django-based software for managing microscopy imaging. OMERO.web before version 5.9.0 loads various information about the current user such as their id, name and the groups they are in, and these are available on the main webclient pages. This represents an information exposure vulnerability. Some additional information being loaded is not used by the webclient and is being removed in this release. This is fixed in version 5.9.0. |
| CVE-2020-7932 | Medium | 2020-06-17 | Not applicable | No public exploit | OMERO.web before 5.6.3 optionally allows sensitive data elements (e.g., a session key) to be passed as URL query parameters. If an attacker tricks a user into clicking a malicious link in OMERO.web, the information in the query parameters may be exposed in the Referer header seen by the target. Information in the URL path such as object IDs may also be exposed. |
| CVE-2019-16245 | Medium | 2020-06-17 | Not applicable | No public exploit | OMERO before 5.6.1 makes the details of each user available to all users. |
| CVE-2018-1000635 | Medium | 2018-08-20 | Not applicable | No public exploit | The Open Microscopy Environment OMERO.server version 5.4.0 to 5.4.6 contains a Information Exposure Through Sent Data vulnerability in OMERO.server that can result in an Attacker gaining full administrative access to server and may be able to disable it. This vulnerability appears to have been fixed in 5.4.7. |