| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Uninitialized resource in WebRTC in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium) |
| In JetBrains IntelliJ IDEA before 2026.3 untrusted projects could read files of other open projects via the built-in web server |
| In JetBrains Ktor before 3.6.1 a DoS attack was possible via the CIO engine |
| In JetBrains YouTrack before 2026.2.19840 improper authorization allowed project administrators to obtain GitLab tokens of other projects |
| In JetBrains YouTrack before 2026.2.19840 app widgets could perform API requests on behalf of viewing users without their consent |
| In JetBrains YouTrack before 2026.2.19840 privilege escalation from project administrator to system administrator was possible via group merging |
| In JetBrains YouTrack before 2026.2.19840 missing authorization allowed guests to add issues to sprints |
| In JetBrains YouTrack before 2026.2.19766 helpdesk email attachments were sent to CC recipients without a visibility check |
| In JetBrains YouTrack before 2026.2.19840 project members could detach inline comment threads of other users on articles |
| modified eCommerce Shopsoftware through 3.3.0 contains a reflected cross-site scripting vulnerability in admin/support.php that allows unauthenticated attackers to inject script via the module parameter. Attackers can trick a logged-in administrator into opening a crafted link to run script in the admin panel, reading CSRF tokens and changing shop settings. |
| modified eCommerce Shopsoftware through 3.3.0 contains a local file inclusion vulnerability that allows administrators to include arbitrary server files by storing ../ sequences in the content manager file name. Unauthenticated requests to shop_content.php then pass the stored path to include(), executing embedded PHP in uploaded content files or images as the web server user. |
| A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to leverage pre-staged malicious content to conduct an XML injection attack due to insufficient parameter validation. A successful exploit could allow an attacker to execute arbitrary commands within the context of the system. This is MTLVULN-1862. |
| A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to conduct an authentication bypass attack due to improper handling of authentication. A successful exploit could allow an attacker to bypass authentication and perform unauthorized actions within the context of the application. This is MTLVULN-1877. |
| When the setting for saving requests to non-existent
pages (404) is enabled, JTL-Shop stores the raw requested URL in its
redirect table, and the administration backend renders it without output
encoding in the form used to edit a redirect. An unauthenticated remote
attacker can store script code with a single request, which is executed in the
browser session of an administrator who opens the affected redirect,
allowing actions to be performed with the administrator's privileges. The
setting is disabled by default in new installations but may still be
enabled in older ones. |
| The visitor tracking of JTL-Shop automatically
registers unknown crawler user agents without filtering the value, and the stored
value is rendered without output encoding on several pages of the
administration backend (search engine statistics, crawler dashboard widget, crawler
edit form, sitemap export download list and campaign details). An
unauthenticated remote attacker can store script code with a single request. The code is
executed in the browser session of an administrator who opens one of these
pages, allowing actions to be performed with the administrator's privileges. |
| The preview mode of the OPC (OnPage Composer) page
builder of JTL-Shop is activated by a request parameter alone and
renders page data supplied in the request without checking for an authenticated
backend session with the corresponding permission. Several portlet properties
are output without output encoding. An unauthenticated remote attacker
can thereby cause script code to be executed in the browser of a
visitor or administrator who opens a crafted link; in the case of an
administrator, actions can be performed with the administrator's privileges. Third-party
plugins whose portlets evaluate property values as templates can
additionally be made to execute template code through the same entry point. This is
a separate flaw in such plugins and does not affect the portlets of JTL-Shop itself. |
| ServiceNow has addressed an indirect prompt injection security issue that was identified in the Email Response AI Agent of Now Assist for CSM. We are not currently aware of malicious exploitation against ServiceNow instances.
This remediation was deployed centrally to the Email Response AI Agent (Now Assist for CSM) and does not require a platform version upgrade or hot fix; no version-specific backports apply. |
| In the Linux kernel, the following vulnerability has been resolved:
scsi: aic79xx: Fix NULL pointer dereference in device reset
Since commit c67e63800446 ("scsi: aic79xx: Do not reference SCSI command
when resetting device") the device reset SCB has no SCSI command, but
ahd_linux_dev_reset() still sets its residual, and ahd_abort_scbs(), which
completes it, sets its status. Seen on an AIC-7902 when a failing disk
triggered a device reset, which killed the SCSI error handler:
BUG: kernel NULL pointer dereference, address: 0000009c
EIP: ahd_linux_dev_reset.cold+0xee/0x26e
Add NULL command checks to the accessors in aic79xx_osm.h. Also skip
autosense for an SCB without a command and complete it with ahd_done()
right away: the REQUEST SENSE path can clear SCB_DEVICE_RESET, after which
ahd_done() would dereference the missing command. |
| In the Linux kernel, the following vulnerability has been resolved:
xfrm4: use a full socket for local errors
xfrm4_local_error() passes skb->sk to inet_sk() and ip_local_error()
without ensuring it points to a full socket. TCP SYN-ACK skbs can be owned
by TCP_NEW_SYN_RECV request sockets.
xfrm4_tunnel_check_size() already checks sk_fullsock() since commit
1620c88887b1 ("xfrm: Fix the usage of skb->sk"), so iptfs_is_too_big() is
the only remaining IPv4 caller passing a request socket here: the sk it
tests is the listener, while skb->sk is the request socket.
When IP-TFS rejects such an skb because it exceeds its payload MTU, the
local error path treats the request socket as a struct inet_sock. KASAN
reports a slab-out-of-bounds read in ip_local_error() beyond the
request_sock_TCP allocation.
Resolve the skb owner with skb_to_full_sk() before accessing inet_sock
state or reporting the error. This maps a request socket to its listener
and rejects sockets that cannot be used as full sockets, matching what
commit 6973a21ee73c ("ipv6: xfrm: use full sockets in local error paths")
did for xfrm6_local_error(). |
| In the Linux kernel, the following vulnerability has been resolved:
drm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()
Since commit 541c8f2468b9 ("dma-buf: detach fence ops on signal v3"),
I'm seeing the BUG_ON() triggering in drm_crtc's fence_to_crtc() via
drm_crtc_fence_get_driver_name() regularly:
Call trace:
panic+0x58/0x5c
die+0x160/0x178
bug_brk_handler+0x70/0xa4
call_el1_break_hook+0x3c/0x1a0
do_el1_brk64+0x24/0x74
el1_brk64+0x34/0x54
el1h_64_sync_handler+0x80/0xfc
el1h_64_sync+0x84/0x88
drm_crtc_fence_get_driver_name+0x60/0x68 (P)
sync_file_get_name+0x184/0x45c
sync_file_ioctl+0x404/0xf70
__arm64_sys_ioctl+0x124/0x1dc
This looks to be caused by a code flow similar to the following:
+++ snip +++
thread A thread B
ioctl(SYNC_IOC_FILE_INFO)
sync_file_ioctl()
sync_file_get_name()
dma_fence_signal_timestamp_locked() dma_fence_driver_name()
ops = rcu_dereference(fence->ops)
if (!dma_fence_test_signaled_flag())
ops->get_driver_name(fence) i.e.
drm_crtc_fence_get_driver_name()
test_and_set_bit(SIGNALED)
RCU_INIT_POINTER(fence->ops, NULL)
drm_crtc_fence_get_driver_name()
BUG_ON(rcu_access_pointer(fence->ops)
!= &drm_crtc_fence_ops)
+++ snap +++
In other words, a fence's ops pointer can now change to NULL on signal,
which wasn't the case before the culprit commit and hence the BUG_ON()
triggers.
Simply drop the BUG_ON() as it's usage of fence ops is invalid now, and
because using BUG_ON() and friends to take down the system is an
unacceptable way to handle a failure.
Note that the adjacent drm_crtc_fence_get_timeline_name() has the same
problem and is fixed by this patch as well. |