Overview 661 matches · 26 in Waratek scope · 7 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
661matches
26in Waratek scope3.9%
7protected1.1%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
7
1.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
19
2.9%
Outside Waratek scope
6
0.9%
Not applicable
629
95.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
7
1.1%
partly blocked
0
0.0%
not blocked
654
98.9%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
661
100.0%
split by
peak 97 / year
19971
Not applicable1
High1
not blocked1
No public exploit1
19985
Not applicable5
High2
Medium3
not blocked5
No public exploit5
19993
Not applicable3
High1
Medium1
Low1
not blocked3
No public exploit3
20000
20013
Not applicable3
High1
Medium2
not blocked3
No public exploit3
20022
Not applicable2
High1
Medium1
not blocked2
No public exploit2
20031
Not applicable1
Medium1
not blocked1
No public exploit1
20042
Not applicable2
Medium2
not blocked2
No public exploit2
20053
Not applicable3
Medium3
not blocked3
No public exploit3
200614
Not applicable14
High4
Medium8
Low2
not blocked14
No public exploit14
200720
Not applicable20
High8
Medium10
Low2
not blocked20
No public exploit20
20087
Not applicable7
High2
Medium5
not blocked7
No public exploit7
20095
Not applicable5
High2
Medium2
Low1
not blocked5
No public exploit5
20108
Not applicable8
High1
Medium7
not blocked8
No public exploit8
20116
No exploit published1
Not applicable5
High2
Medium4
not blocked6
No public exploit6
201214
Not applicable14
High3
Medium10
Low1
not blocked14
No public exploit14
201311
Not applicable11
High1
Medium9
Low1
not blocked11
No public exploit11
201410
Not applicable10
High1
Medium9
not blocked10
No public exploit10
201511
Not applicable11
High1
Medium9
Low1
not blocked11
No public exploit11
20163
Not applicable3
Critical1
High1
Medium1
not blocked3
No public exploit3
201721
Not applicable21
Critical1
High13
Medium7
not blocked21
No public exploit21
201816
Protected by Waratek1
No exploit published1
Not applicable14
Critical2
High5
Medium7
Low2
blocked by ARMR today1
not blocked15
No public exploit16
201947
Protected by Waratek3
No exploit published2
Outside Waratek scope4
Not applicable38
Critical11
High16
Medium20
blocked by ARMR today3
not blocked44
No public exploit47
202044
Protected by Waratek1
No exploit published3
Outside Waratek scope1
Not applicable39
Critical4
High17
Medium21
Low2
blocked by ARMR today1
not blocked43
No public exploit44
202159
Protected by Waratek2
No exploit published5
Outside Waratek scope1
Not applicable51
Critical7
High23
Medium29
blocked by ARMR today2
not blocked57
No public exploit59
202257
No exploit published1
Not applicable56
Critical10
High22
Medium25
not blocked57
No public exploit57
202397
No exploit published1
Not applicable96
Critical22
High22
Medium53
not blocked97
No public exploit97
202463
Not applicable63
Critical7
High20
Medium36
not blocked63
No public exploit63
202539
No exploit published5
Not applicable34
High21
Medium17
Low1
not blocked39
No public exploit39
202689
Not applicable89
Critical7
High28
Medium50
Low4
not blocked89
No public exploit89
1999200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-103497 | Medium | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 sSRF was possible via the GitHub VCS integration |
| CVE-2026-103496 | Medium | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 iDOR in inbox threads allowed reading other users' notifications |
| CVE-2026-103495 | Medium | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 missing authorisation allowed reloading of translation catalogs |
| CVE-2026-103494 | Medium | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 privilege escalation was possible via user group membership changes |
| CVE-2026-103493 | High | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 stored XSS via Mermaid and LaTeX content was possible |
| CVE-2026-103492 | Medium | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 doS attack was possible via crafted PSD attachments |
| CVE-2026-103491 | Medium | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 iDOR in the issue activities API allowed reading restricted issues |
| CVE-2026-103490 | High | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 privilege escalation was possible via user group links |
| CVE-2026-103489 | Medium | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 hTML injection in VCS command failure notifications was possible |
| CVE-2026-103488 | High | 2026-10-01 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19422 missing authorisation allowed authenticated users to add themselves to project teams and access restricted issues |
| CVE-2026-100280 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 creating a project from an unreadable custom template was possible |
| CVE-2026-100279 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 changing an integration URL exposed its stored credentials |
| CVE-2026-100278 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 users with restricted permission could edit and hide other users' comments |
| CVE-2026-100277 | Critical | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 account takeover was possible by replaying a notification signature |
| CVE-2026-100276 | High | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 guest users could remove a workflow action's visibility restriction and run the action |
| CVE-2026-100275 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 stored XSS in the workflow error notification toast was possible |
| CVE-2026-100274 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 project Admin could trigger DoS via a notification template |
| CVE-2026-100273 | Critical | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 authorisation bypass in the scripts debugger allowed arbitrary code execution |
| CVE-2026-100272 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 missing authorisation in the notification template preview allowed Project Administrators to read restricted issues |
| CVE-2026-100271 | Low | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 missing authorisation on several endpoints allowed authenticated users to access information from other projects |
| CVE-2026-100270 | Low | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 low-level Admin Read permission users could disclose integration credentials via import configurations |
| CVE-2026-100269 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 helpdesk project's Authorized Reporters list could be bypassed |
| CVE-2026-100268 | High | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 project administrators could read comments from other projects via notification templates |
| CVE-2026-100267 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.19197 reDoS attack was possible via mailbox regex mail-rule filters |
| CVE-2026-100264 | Low | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 stored SMTP server credentials could be disclosed by changing the server host |
| CVE-2026-100263 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 stored HTML injection via the User-Agent header was possible |
| CVE-2026-100262 | High | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 missing authorisation allowed users with read-only project access to overwrite project notification templates |
| CVE-2026-100261 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 changing article visibility settings was possible without update permission |
| CVE-2026-100260 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 mailbox integration allowed authentication after a password reset |
| CVE-2026-100259 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 improper access control on Gantt chart allowed edits by users with view-only access |
| CVE-2026-100258 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 missing authorisation allowed read-only users to read project settings |
| CVE-2026-100257 | Medium | 2026-09-30 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18991 sSRF via stored XHTML injection was possible during PDF export |
| CVE-2026-75051 | High | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.17917 unauthorised project transfer between organisations was possible |
| CVE-2026-75050 | High | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13901, 2026.2.17950 doS attack was possible via crafted type parameters |
| CVE-2026-75049 | Medium | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13903, 2026.2.17950 an authenticated user could read restricted articles from other projects via the draft creation endpoint |
| CVE-2026-75048 | High | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18068 stored XSS via the fenced code-block language label was possible |
| CVE-2026-75047 | Medium | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18177 doS attack was possible via a decompression bomb in the import endpoint |
| CVE-2026-75046 | Medium | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.18112 an authenticated user could enumerate accounts via the users search endpoint |
| CVE-2026-75045 | Critical | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.156085, 2026.1.13913, 2026.2.18112 an unauthenticated attacker could download database backups via shared draft signature |
| CVE-2026-75044 | High | 2026-08-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.156085, 2026.1.13914, 2026.2.18095 missing authorisation allowed an authenticated user to delete arbitrary entities via the mailbox endpoint |
| CVE-2026-44231 | Critical | 2026-07-20 | Not applicable | No public exploit | RT is an open source, enterprise-grade issue and ticket tracking system. Versions prior to 5.0.10, 6.0.0 and above, prior to 6.0.3 contain an information disclosure and privilege escalation vulnerability in the REST 2.0 API. A privileged (non-administrative) user can obtain authentication credentials belonging to other users — including users with administrative privileges — and use those credentials to read data as those users via RT's feed endpoints. The same request that exposes the credentials also rotates them, invalidating previously-distributed feed URLs across the instance. This issue has been fixed in versions 5.0.10 and 6.0.3. |
| CVE-2026-44230 | Medium | 2026-07-20 | Not applicable | No public exploit | RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.4 up to (but not including) 5.0.10, and 6.0.0 up to (but not including) 6.0.3 contain a reflected Cross-Site Scripting (XSS) vulnerability where an attacker who can induce an authenticated RT user to visit a crafted URL can execute arbitrary JavaScript in that user's browser session. This issue has been fixed in versions 5.0.10 and 6.0.3. |
| CVE-2026-44229 | Medium | 2026-07-20 | Not applicable | No public exploit | RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.0 and 6.0.0 and above, prior to both 5.0.10 and 6.0.3 contain a Cross-Site Scripting (XSS) vulnerability where uploaded content is served inline rather than as an attachment. An authenticated user who can upload content can include JavaScript in the upload that will execute in the browser session of any RT user who later views or downloads it. This issue has been fixed in versions 5.0.10 and 6.0.3. |
| CVE-2026-44228 | Medium | 2026-07-20 | Not applicable | No public exploit | RT is an open source, enterprise-grade issue and ticket tracking system. Versions 6.0.0 and above, prior to 6.0.3, contain a stored Cross-Site Scripting (XSS) vulnerability, where user-controlled data is rendered without proper HTML escaping. An authenticated user with permission to set the relevant data can inject JavaScript that executes when another RT user views the affected page. This issue has been fixed in version 6.0.3. |
| CVE-2026-44227 | Medium | 2026-07-20 | Not applicable | No public exploit | RT is an open source, enterprise-grade issue and ticket tracking system. Versions 6.0.0 and above, prior to 6.0.3 contain a reflected Cross-Site Scripting (XSS) vulnerability. An attacker who can induce an authenticated RT user to visit a crafted URL can execute arbitrary JavaScript in that user's browser session. There are no effective workarounds. Avoid following untrusted RT URLs. This issue has been fixed in version 6.0.3. |
| CVE-2026-62422 | Critical | 2026-07-14 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 authentication bypass via direct database access leading to administrative access was possible |
| CVE-2026-61492 | Medium | 2026-07-10 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.17394 stored XSS via article titles in digest emails was possible |
| CVE-2026-59791 | Low | 2026-07-10 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.17012 cSS injection via Mermaid diagram rendering was possible |
| CVE-2026-57926 | Critical | 2026-06-26 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.16593 the websandbox bridge was vulnerable to a prototype pollution attack |
| CVE-2026-57925 | Medium | 2026-06-26 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.16593 improper access control allowed reading saved queries and tags |
| CVE-2026-57924 | Medium | 2026-06-26 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.16593 default role configuration exposed excessive user profile details |
| CVE-2026-57923 | High | 2026-06-26 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.16593 improper authorisation in the app configurations endpoint allowed modifying project settings |
| CVE-2026-57922 | Medium | 2026-06-26 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.16593 project settings disclosure via the MCP was possible |
| CVE-2026-57921 | High | 2026-06-26 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.2.16593 improper access control allowed reading users' private data via the comment templates endpoint |
| CVE-2025-32748 | Medium | 2026-06-17 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) prior to 5.1.0.1, contain(s) a Host Header Injection vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability to trigger redirections. |
| CVE-2026-49386 | Medium | 2026-05-29 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13570 improper access control allowed enumeration of restricted issues and articles on Planning Canvas |
| CVE-2026-49385 | Medium | 2026-05-29 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13570 improper access control allowed low-privileged users to modify service accounts |
| CVE-2026-49370 | High | 2026-05-29 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13162 information disclosure was possible on fetchApp requests |
| CVE-2026-49369 | Medium | 2026-05-29 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13162 information disclosure was possible on Users and Groups pages |
| CVE-2026-49368 | High | 2026-05-29 | Not applicable | No public exploit | In JetBrains YouTrack before 2026.1.13162 stored XSS in project notification templates was possible |
| CVE-2025-46371 | Medium | 2026-05-22 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) a Use of a Broken or Risky Cryptographic Algorithm vulnerability in the ssh. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Protection mechanism bypass. |
| CVE-2025-32751 | Medium | 2026-05-22 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) an Insecure Storage of Sensitive Information vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to unauthorized access to sensitive information. |
| CVE-2025-32749 | High | 2026-05-22 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) an Exposure of Information Through Directory Listing vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Information exposure. |
| CVE-2025-32747 | High | 2026-05-22 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) an Incorrect Privilege Assignment vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Elevation of privileges. |
| CVE-2025-32746 | Medium | 2026-05-22 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) an Insecure Storage of Sensitive Information vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to unauthorized access to sensitive information. |
| CVE-2025-32745 | Medium | 2026-05-22 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) an Improper Certificate Validation vulnerability. An unauthenticated attacker with adjacent network access could potentially exploit this vulnerability, leading to Information tampering. |
| CVE-2025-26483 | High | 2026-05-22 | Not applicable | No public exploit | Dell PowerFlex Manager, versions 4.6.2 and prior, contains an Open Redirect Vulnerability. An unauthenticated attacker could potentially exploit this vulnerability, leading to a targeted application user being redirected to arbitrary web URLs. The vulnerability could be leveraged by attackers to conduct phishing attacks that cause users to divulge sensitive information. |
| CVE-2026-6841 | Medium | 2026-05-21 | Not applicable | No public exploit | Request Tracker is vulnerable to a reflected cross-site scripting (XSS) vulnerability via the "Page" parameter in GET requests. An attacker can craft a URL that, when opened, results in arbitrary JavaScript execution in the victim’s browser. This vulnerability affects versions from 5.0.4 up to 5.0.9 and from 6.0.0 up to 6.0.2. |
| CVE-2025-32750 | High | 2026-05-20 | Not applicable | No public exploit | Dell PowerFlex Manager, version(s) <=4.6.2, contain(s) an Exposure of Information Through Directory Listing vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Information exposure. |
| CVE-2026-33392 | High | 2026-04-17 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.131383 high privileged user can achieve RCE via sandbox bypass |
| CVE-2026-5747 | High | 2026-04-08 | Not applicable | No public exploit | An out-of-bounds write issue in the virtio PCI transport in Firecracker 1.13.0 through 1.14.3 and 1.15.0 on x86_64 and aarch64 might allow a local guest user with root privileges to crash the Firecracker VMM process or potentially execute arbitrary code on the host via modification of virtio queue configuration registers after device activation. Achieving code execution on the host requires additional preconditions, such as the use of a custom guest kernel or specific snapshot configurations. To remediate this, users should upgrade to Firecracker 1.14.4 or 1.15.1 and later. |
| CVE-2026-39324 | Critical | 2026-04-07 | Not applicable | No public exploit | Rack::Session is a session management implementation for Rack. From 2.0.0 to before 2.1.2, Rack::Session::Cookie incorrectly handles decryption failures when configured with secrets:. If cookie decryption fails, the implementation falls back to a default decoder instead of rejecting the cookie. This allows an unauthenticated attacker to supply a crafted session cookie that is accepted as valid session data without knowledge of any configured secret. Because this mechanism is used to load session state, an attacker can manipulate session contents and potentially gain unauthorized access. This vulnerability is fixed in 2.1.2. |
| CVE-2026-34831 | Medium | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Files#fail sets the Content-Length response header using String#size instead of String#bytesize. When the response body contains multibyte UTF-8 characters, the declared Content-Length is smaller than the number of bytes actually sent on the wire. Because Rack::Files reflects the requested path in 404 responses, an attacker can trigger this mismatch by requesting a non-existent path containing percent-encoded UTF-8 characters. This results in incorrect HTTP response framing and may cause response desynchronization in deployments that rely on the incorrect Content-Length value. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-34830 | High | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Sendfile#map_accel_path interpolates the value of the X-Accel-Mapping request header directly into a regular expression when rewriting file paths for X-Accel-Redirect. Because the header value is not escaped, an attacker who can supply X-Accel-Mapping to the backend can inject regex metacharacters and control the generated X-Accel-Redirect response header. In deployments using Rack::Sendfile with x-accel-redirect, this can allow an attacker to cause nginx to serve unintended files from configured internal locations. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-34829 | High | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Multipart::Parser only wraps the request body in a BoundedIO when CONTENT_LENGTH is present. When a multipart/form-data request is sent without a Content-Length header, such as with HTTP chunked transfer encoding, multipart parsing continues until end-of-stream with no total size limit. For file parts, the uploaded body is written directly to a temporary file on disk rather than being constrained by the buffered in-memory upload limit. An unauthenticated attacker can therefore stream an arbitrarily large multipart file upload and consume unbounded disk space. This results in a denial of service condition for Rack applications that accept multipart form data. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-34827 | High | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. From versions 3.0.0.beta1 to before 3.1.21, and 3.2.0 to before 3.2.6, Rack::Multipart::Parser#handle_mime_head parses quoted multipart parameters such as Content-Disposition: form-data; name="..." using repeated String#index searches combined with String#slice! prefix deletion. For escape-heavy quoted values, this causes super-linear processing. An unauthenticated attacker can send a crafted multipart/form-data request containing many parts with long backslash-escaped parameter values to trigger excessive CPU usage during multipart parsing. This results in a denial of service condition in Rack applications that accept multipart form data. This issue has been patched in versions 3.1.21 and 3.2.6. |
| CVE-2026-34826 | High | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Utils.get_byte_ranges parses the HTTP Range header without limiting the number of individual byte ranges. Although the existing fix for CVE-2024-26141 rejects ranges whose total byte coverage exceeds the file size, it does not restrict the count of ranges. An attacker can supply many small overlapping ranges such as 0-0,0-0,0-0,... to trigger disproportionate CPU, memory, I/O, and bandwidth consumption per request. This results in a denial of service condition in Rack file-serving paths that process multipart byte range responses. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-34786 | Medium | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Static#applicable_rules evaluates several header_rules types against the raw URL-encoded PATH_INFO, while the underlying file-serving path is decoded before the file is served. As a result, a request for a URL-encoded variant of a static path can serve the same file without the headers that header_rules were intended to apply. In deployments that rely on Rack::Static to attach security-relevant response headers to static content, this can allow an attacker to bypass those headers by requesting an encoded form of the path. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-34785 | High | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Static determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as "/css", it matches any request path that begins with that string, including unrelated paths such as "/css-config.env" or "/css-backup.sql". As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-34763 | Medium | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Directory interpolates the configured root path directly into a regular expression when deriving the displayed directory path. If root contains regex metacharacters such as +, *, or ., the prefix stripping can fail and the generated directory listing may expose the full filesystem path in the HTML output. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-34230 | High | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Utils.select_best_encoding processes Accept-Encoding values with quadratic time complexity when the header contains many wildcard (*) entries. Because this method is used by Rack::Deflater to choose a response encoding, an unauthenticated attacker can send a single request with a crafted Accept-Encoding header and cause disproportionate CPU consumption on the compression middleware path. This results in a denial of service condition for applications using Rack::Deflater. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-32762 | Medium | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. From versions 3.0.0.beta1 to before 3.1.21 and 3.2.0 to before 3.2.6, Rack::Utils.forwarded_values parses the RFC 7239 Forwarded header by splitting on semicolons before handling quoted-string values. Because quoted values may legally contain semicolons, a header can be interpreted by Rack as multiple Forwarded directives rather than as a single quoted for value. In deployments where an upstream proxy, WAF, or intermediary validates or preserves quoted Forwarded values differently, this discrepancy can allow an attacker to smuggle host, proto, for, or by parameters through a single header value. This issue has been patched in versions 3.1.21 and 3.2.6. |
| CVE-2026-26962 | Medium | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. From version 3.2.0 to before version 3.2.6, Rack::Multipart::Parser unfolds folded multipart part headers incorrectly. When a multipart header contains an obs-fold sequence, Rack preserves the embedded CRLF in parsed parameter values such as filename or name instead of removing the folded line break during unfolding. As a result, applications that later reuse those parsed values in HTTP response headers may be vulnerable to downstream header injection or response splitting. This issue has been patched in version 3.2.6. |
| CVE-2026-26961 | Medium | 2026-04-02 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Multipart::Parser extracts the boundary parameter from multipart/form-data using a greedy regular expression. When a Content-Type header contains multiple boundary parameters, Rack selects the last one rather than the first. In deployments where an upstream proxy, WAF, or intermediary interprets the first boundary parameter, this mismatch can allow an attacker to smuggle multipart content past upstream inspection and have Rack parse a different body structure than the intermediary validated. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6. |
| CVE-2026-28193 | High | 2026-02-25 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.121962 apps were able to send requests to the app permissions endpoint |
| CVE-2026-25500 | Medium | 2026-02-18 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, `Rack::Directory` generates an HTML directory index where each file entry is rendered as a clickable link. If a file exists on disk whose basename starts with the `javascript:` scheme (e.g. `javascript:alert(1)`), the generated index contains an anchor whose `href` is exactly `javascript:alert(1)`. Clicking the entry executes JavaScript in the browser (demonstrated with `alert(1)`). Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue. |
| CVE-2026-22860 | High | 2026-02-18 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, `Rack::Directory`’s path check used a string prefix match on the expanded path. A request like `/../root_example/` can escape the configured root if the target path starts with the root string, allowing directory listing outside the intended root. Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue. |
| CVE-2026-25846 | Medium | 2026-02-09 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.119033 access tokens could be exposed in Mailbox logs |
| CVE-2026-1386 | Medium | 2026-01-23 | Not applicable | No public exploit | A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above. |
| CVE-2025-64773 | Low | 2025-11-11 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.104432 a race condition allowed bypass of helpdesk Agent limit |
| CVE-2025-64685 | High | 2025-11-10 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.104432 missing TLS certificate validation enabled data disclosure |
| CVE-2025-64684 | High | 2025-11-10 | Not applicable | No public exploit | In JetBrains YouTrack before 2025.3.104432 information disclosure was possible via the feedback form |
| CVE-2025-10927 | Medium | 2025-10-30 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Plausible tracking allows Cross-Site Scripting (XSS).This issue affects Plausible tracking: from 0.0.0 before 1.0.2. |
| CVE-2025-62244 | Medium | 2025-10-13 | No exploit published | No public exploit | Insecure direct object reference (IDOR) vulnerability in Publications in Liferay Portal 7.3.1 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92, and 7.3 GA through update 36 allows remote authenticated attackers to view the edit page of a publication via the _com_liferay_change_tracking_web_portlet_PublicationsPortlet_ctCollectionId parameter. |
| CVE-2025-62243 | Medium | 2025-10-13 | No exploit published | No public exploit | Insecure direct object reference (IDOR) vulnerability in Publications in Liferay Portal 7.4.1 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92 allows remote authenticated attackers to view publication comments via the _com_liferay_change_tracking_web_portlet_PublicationsPortlet_value parameter. Publications comments in Liferay Portal 7.4.1 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92 does not properly check user permissions, which allows remote authenticated users to edit publication comments via crafted URLs. |
| CVE-2025-62242 | Medium | 2025-10-13 | No exploit published | No public exploit | Insecure Direct Object Reference (IDOR) vulnerability with account addresses in Liferay Portal 7.4.3.4 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92 allows remote authenticated users to from one account to view addresses from a different account via the _com_liferay_account_admin_web_internal_portlet_AccountEntriesAdminPortlet_addressId parameter. |
| CVE-2025-62245 | Medium | 2025-10-10 | No exploit published | No public exploit | Cross-site request forgery (CSRF) vulnerability in Liferay Portal 7.4.1 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.10, and 7.4 GA through update 92 allows remote attackers to add and edit publication comments. |
| CVE-2025-61919 | High | 2025-10-10 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, `Rack::Request#POST` reads the entire request body into memory for `Content-Type: application/x-www-form-urlencoded`, calling `rack.input.read(nil)` without enforcing a length or cap. Large request bodies can therefore be buffered completely into process memory before parsing, leading to denial of service (DoS) through memory exhaustion. Users should upgrade to Rack version 2.2.20, 3.1.18, or 3.2.3, anu of which enforces form parameter limits using `query_parser.bytesize_limit`, preventing unbounded reads of `application/x-www-form-urlencoded` bodies. Additionally, enforce strict maximum body size at the proxy or web server layer (e.g., Nginx `client_max_body_size`, Apache `LimitRequestBody`). |
| CVE-2025-61780 | Medium | 2025-10-10 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely. |
| CVE-2025-61772 | High | 2025-10-07 | Not applicable | No public exploit | Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, `Rack::Multipart::Parser` can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (`CRLFCRLF`). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS). Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected. Versions 2.2.19, 3.1.17, and 3.2.2 cap per-part header size (e.g., 64 KiB). As a workaround, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx `client_max_body_size`). |