Monthly
Grafana OSS and Grafana Enterprise 13.2 installations that have explicitly enabled the experimental kubernetesSsoSettingsApi feature toggle let any authenticated user read SSO client secrets and modify instance-wide SSO configuration, because the SSO settings endpoints are missing an authorization check (CWE-285). Default deployments are not exposed, since the toggle ships disabled, and an attacker needs a valid Grafana account but not the SSO-settings permission that should normally be enforced. No public exploit code or confirmed active exploitation has been identified at time of analysis; the Grafana security advisory is the authoritative reference for fixed releases and any interim guidance.
Snipe-IT 8.6.2 and earlier can re-admit deactivated accounts - including accounts with admin rights - through the Google SSO callback, because GoogleAuthController::handleGoogleCallback logged in whichever local user matched the incoming Google email as a username without enforcing the activated flag. The exposure is gated by deployment shape: Google SSO must be enabled, the instance must use email-as-username (or the targeted account must have an email-shaped username), the Snipe-IT account must already be deactivated, and the attacker must still hold a live, unrevoked Google Workspace identity for that address. Default installations that use the firstname.lastname username format are not affected because the username/email mismatch makes the lookup return NULL; this makes the bug primarily an offboarding-window and former-insider risk rather than anonymous external compromise, and it has been assigned an act_now priority. No public exploit code was identified at time of analysis, and the issue is fixed in Snipe-IT 8.6.3 via commit 5fea2fadc0.
obsidian-tc 1.13.0 through 1.31.3 lets an authenticated client complete destructive, dispatch-gated Obsidian vault operations (delete, cross-folder move, frontmatter replace, link rewrite) even after the human explicitly declined or cancelled the human-in-the-loop confirmation, or after the elicitation response was omitted or malformed. The server treats a validly bound requestState echoed on resubmission as proof of approval, but that state is minted before the elicitation leg is ever asked, so it only proves the resubmission belongs to the same call; exploitation requires a Streamable HTTP deployment with auth.jwtSecret configured, a 2026-07-28-era client declaring elicitation.form support, and a tool marked destructive:true or carrying a human-in-the-loop scope floor. Only client-driven HTTP deployments are affected - stdio or jwtSecret-unset installs fall back to the CLI elicit_token path and never offer the round trip - and there is no public exploit identified at time of analysis (no CISA KEV listing), though the advisory notes the underlying construction was reproduced directly by the maintainers.
Any account holding the lowest 'member' role in a PraisonAI Platform workspace can permanently delete projects, agents, issues, labels, issue dependencies and issue-label attachments created by the workspace owner or by other members, because all six content DELETE endpoints verify workspace membership but never verify resource ownership or an owner/admin role. The flaw affects praisonai-platform from 0.1.4 up to the fix and scores CVSS 8.1 (AV:N/AC:L/PR:L/UI:N/C:N/I:H/A:H), since an authenticated low-privileged user can destroy integrity and availability of workspace content while confidentiality is untouched. Exploitation requires a valid member account inside the targeted workspace - either invited by the victim or obtained through a compromised member credential - so the practical exposure is an insider or account-takeover scenario rather than a mass internet threat; there is no CISA KEV entry, no EPSS signal supplied and no confirmed working exploit package, though the vendor advisory publishes a full step-by-step reproduction.
Remote unauthenticated denial of service in Apache bRPC through 1.17.0 lets a network peer crash an HTTP/2 or gRPC (h2) server by sending a crafted sequence of minimal HPACK header entries. The default 4096-byte HPACK dynamic table is allocated as 120 slots based on a 34-byte entry size, while the true minimum entry is 33 bytes, so 121 minimal entries fit within the byte cap without triggering eviction and then hit a full-header-queue CHECK that aborts the process. No authentication or user interaction is required; bRPC 1.18.0 and upstream patch PR #3462 correct the sizing, and no public exploit code or CISA KEV entry was identified in the provided data.
Oracle Solaris 11.4's Image Packaging System (IPS) can be induced to act on attacker-influenced package content delivered over HTTP, giving a network-positioned, unauthenticated attacker high confidentiality impact and limited integrity impact (CVSS 3.1: 7.1 High, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N). The attacker must either control or compromise the repository the host queries, or intercept cleartext HTTP package traffic, and exploitation still requires a Solaris operator to perform a package operation against that content - the UI:R condition is the decisive exposure limiter. Only Solaris 11.4 is listed as affected per Oracle's October 2026 CPU and ENISA EUVD; no public exploit code was identified in the provided intelligence at time of analysis.
Unauthenticated remote write access in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an attacker manipulate the shared Redis backing store under any tenant's key, collapsing the platform's credential-encryption boundary and allowing cached flow parameters to be poisoned across tenants. The issue is rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) and requires the multi-tenant deployment pattern where tenants share the same Redis instance. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.
Cross-domain sender spoofing in Mailu allows a domain manager to authenticate as arbitrary senders on other domains hosted on the same instance. The flaw is an improper-authorization issue in which the Postfix sender-login lookup honors the allow_spoofing flag globally rather than scoping it to the requesting user's own domain, so a manager of one hosted domain can enable spoofing and pass DKIM/SPF authentication for domains they do not own. Exploitation requires an existing domain-manager (administrative) role (CVSS PR:H) on a multi-tenant deployment hosting more than one domain; there is no unauthenticated or end-user path, and no public exploit code was identified at time of analysis.
Mailu, an open-source mail server distributed as a set of Docker images, contains an authorization flaw that lets an authenticated domain manager reset the password of, or mint an API token for, a higher-privileged account that merely owns a mailbox in a domain they manage - including a global admin or a manager of another domain. Because the vulnerable endpoints are the user edit, password reset, and token creation flows, a successful attack grants full control of the victim account and all of its privileges, escalating a limited domain-manager role into global administrative control; the CVSS 3.1 vector is 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires valid domain-manager credentials and the specific condition that a higher-privileged user owns a mailbox inside the attacker's managed domain, so single-tenant installs with no delegated domain managers are effectively not exposed; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Unauthenticated attackers who know the shared identifier of a public, password-protected Lychee album can pull down a ZIP archive of the album's photos via GET /api/v2/Zip without ever supplying the album password, because the download authorization path never re-checks album access. All versions prior to 7.6.3 are affected, and the exposure escalates to full-resolution originals plus associated metadata when the album's grants_full_photo_access flag is also enabled. The flaw only triggers on a non-default sharing configuration (public + password-protected + grants_download on), and no public exploit identified at time of analysis; the vendor fix is 7.6.3.
Grafana OSS and Grafana Enterprise 13.2 installations that have explicitly enabled the experimental kubernetesSsoSettingsApi feature toggle let any authenticated user read SSO client secrets and modify instance-wide SSO configuration, because the SSO settings endpoints are missing an authorization check (CWE-285). Default deployments are not exposed, since the toggle ships disabled, and an attacker needs a valid Grafana account but not the SSO-settings permission that should normally be enforced. No public exploit code or confirmed active exploitation has been identified at time of analysis; the Grafana security advisory is the authoritative reference for fixed releases and any interim guidance.
Snipe-IT 8.6.2 and earlier can re-admit deactivated accounts - including accounts with admin rights - through the Google SSO callback, because GoogleAuthController::handleGoogleCallback logged in whichever local user matched the incoming Google email as a username without enforcing the activated flag. The exposure is gated by deployment shape: Google SSO must be enabled, the instance must use email-as-username (or the targeted account must have an email-shaped username), the Snipe-IT account must already be deactivated, and the attacker must still hold a live, unrevoked Google Workspace identity for that address. Default installations that use the firstname.lastname username format are not affected because the username/email mismatch makes the lookup return NULL; this makes the bug primarily an offboarding-window and former-insider risk rather than anonymous external compromise, and it has been assigned an act_now priority. No public exploit code was identified at time of analysis, and the issue is fixed in Snipe-IT 8.6.3 via commit 5fea2fadc0.
obsidian-tc 1.13.0 through 1.31.3 lets an authenticated client complete destructive, dispatch-gated Obsidian vault operations (delete, cross-folder move, frontmatter replace, link rewrite) even after the human explicitly declined or cancelled the human-in-the-loop confirmation, or after the elicitation response was omitted or malformed. The server treats a validly bound requestState echoed on resubmission as proof of approval, but that state is minted before the elicitation leg is ever asked, so it only proves the resubmission belongs to the same call; exploitation requires a Streamable HTTP deployment with auth.jwtSecret configured, a 2026-07-28-era client declaring elicitation.form support, and a tool marked destructive:true or carrying a human-in-the-loop scope floor. Only client-driven HTTP deployments are affected - stdio or jwtSecret-unset installs fall back to the CLI elicit_token path and never offer the round trip - and there is no public exploit identified at time of analysis (no CISA KEV listing), though the advisory notes the underlying construction was reproduced directly by the maintainers.
Any account holding the lowest 'member' role in a PraisonAI Platform workspace can permanently delete projects, agents, issues, labels, issue dependencies and issue-label attachments created by the workspace owner or by other members, because all six content DELETE endpoints verify workspace membership but never verify resource ownership or an owner/admin role. The flaw affects praisonai-platform from 0.1.4 up to the fix and scores CVSS 8.1 (AV:N/AC:L/PR:L/UI:N/C:N/I:H/A:H), since an authenticated low-privileged user can destroy integrity and availability of workspace content while confidentiality is untouched. Exploitation requires a valid member account inside the targeted workspace - either invited by the victim or obtained through a compromised member credential - so the practical exposure is an insider or account-takeover scenario rather than a mass internet threat; there is no CISA KEV entry, no EPSS signal supplied and no confirmed working exploit package, though the vendor advisory publishes a full step-by-step reproduction.
Remote unauthenticated denial of service in Apache bRPC through 1.17.0 lets a network peer crash an HTTP/2 or gRPC (h2) server by sending a crafted sequence of minimal HPACK header entries. The default 4096-byte HPACK dynamic table is allocated as 120 slots based on a 34-byte entry size, while the true minimum entry is 33 bytes, so 121 minimal entries fit within the byte cap without triggering eviction and then hit a full-header-queue CHECK that aborts the process. No authentication or user interaction is required; bRPC 1.18.0 and upstream patch PR #3462 correct the sizing, and no public exploit code or CISA KEV entry was identified in the provided data.
Oracle Solaris 11.4's Image Packaging System (IPS) can be induced to act on attacker-influenced package content delivered over HTTP, giving a network-positioned, unauthenticated attacker high confidentiality impact and limited integrity impact (CVSS 3.1: 7.1 High, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N). The attacker must either control or compromise the repository the host queries, or intercept cleartext HTTP package traffic, and exploitation still requires a Solaris operator to perform a package operation against that content - the UI:R condition is the decisive exposure limiter. Only Solaris 11.4 is listed as affected per Oracle's October 2026 CPU and ENISA EUVD; no public exploit code was identified in the provided intelligence at time of analysis.
Unauthenticated remote write access in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an attacker manipulate the shared Redis backing store under any tenant's key, collapsing the platform's credential-encryption boundary and allowing cached flow parameters to be poisoned across tenants. The issue is rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) and requires the multi-tenant deployment pattern where tenants share the same Redis instance. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.
Cross-domain sender spoofing in Mailu allows a domain manager to authenticate as arbitrary senders on other domains hosted on the same instance. The flaw is an improper-authorization issue in which the Postfix sender-login lookup honors the allow_spoofing flag globally rather than scoping it to the requesting user's own domain, so a manager of one hosted domain can enable spoofing and pass DKIM/SPF authentication for domains they do not own. Exploitation requires an existing domain-manager (administrative) role (CVSS PR:H) on a multi-tenant deployment hosting more than one domain; there is no unauthenticated or end-user path, and no public exploit code was identified at time of analysis.
Mailu, an open-source mail server distributed as a set of Docker images, contains an authorization flaw that lets an authenticated domain manager reset the password of, or mint an API token for, a higher-privileged account that merely owns a mailbox in a domain they manage - including a global admin or a manager of another domain. Because the vulnerable endpoints are the user edit, password reset, and token creation flows, a successful attack grants full control of the victim account and all of its privileges, escalating a limited domain-manager role into global administrative control; the CVSS 3.1 vector is 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires valid domain-manager credentials and the specific condition that a higher-privileged user owns a mailbox inside the attacker's managed domain, so single-tenant installs with no delegated domain managers are effectively not exposed; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Unauthenticated attackers who know the shared identifier of a public, password-protected Lychee album can pull down a ZIP archive of the album's photos via GET /api/v2/Zip without ever supplying the album password, because the download authorization path never re-checks album access. All versions prior to 7.6.3 are affected, and the exposure escalates to full-resolution originals plus associated metadata when the album's grants_full_photo_access flag is also enabled. The flaw only triggers on a non-default sharing configuration (public + password-protected + grants_download on), and no public exploit identified at time of analysis; the vendor fix is 7.6.3.