Improper validation of client-supplied transaction fields in the mppx fee-payer sponsorship path (src/tempo/internal/fee-payer.ts) allows an unauthenticated client to inflate the gas fees paid by a server's fee_payer wallet before version 0.8.2. Any deployment operating a hosted fee-payer/cosigning endpoint that accepts 0x78 FeePayerEnvelope submissions is affected; the attacker simply appends fabricated address-only EIP-2930 access-list entries whose intrinsic gas cost is charged to the sponsor, with a demonstrated 180-entry list raising the fee roughly 9.4x while remaining under the 500,000-gas policy cap, the 16 KB header limit, and the RPC simulation budget. Impact is limited to a bounded financial/availability drain on the sponsor wallet (no confidentiality, integrity, or code-execution impact), no public exploit code has been identified at time of analysis, and the issue is fixed in mppx 0.8.2.
Fee-sponsoring servers built on mppx before 0.8.2 can be induced by any client with access to the sponsorship endpoint to pay roughly five times the intended gas fee on otherwise-valid transactions. The FeePayerPolicy validator in src/tempo/internal/fee-payer.ts decoded client-supplied calldata with viem's decodeFunctionData but never rejected trailing bytes, so an attacker could append nonzero padding to a legitimate tip20/stablecoinDex call (transfer, approve, transferWithMemo, swapExactAmountOut) and inflate intrinsic calldata gas while gas_limit and max_fee_per_gas stayed inside the policy caps the server checks. Exploitation is unauthenticated and requires no user interaction, but impact is inherently bounded economic griefing: the demonstrated overpayment was limited to about 5x by the 16KB header ceiling (~5,500 padding bytes), and only operators who actually offer fee sponsorship are exposed. No public exploit code was identified at time of analysis and the issue is fixed in 0.8.2.
Stored cross-site scripting in the Text Styler WordPress plugin (all versions through 1.1.1) allows an authenticated user with contributor-level capabilities or above to save JavaScript inside a styling value that the plugin renders unescaped in a front-end style block, so the payload executes in the browser of anyone who views the affected post - including administrators. A secondary defect compounds the issue: the plugin does not verify that the user is permitted to edit the target post, so a low-privileged contributor can plant the payload on content they do not own. Exploitation requires only a valid contributor+ account and a victim viewing the crafted post (UI:R) on a site with this niche plugin installed; publicly available exploit code exists, and no public exploit is confirmed as actively exploited and the flaw is not listed in CISA KEV. Our independent assessment rates this moderate risk at CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N.
Notepad++ releases prior to 8.9.8 enforce their shortcuts.xml HMAC integrity check on the Macro menu and keyboard-shortcut paths but omit it on the WM_MACRODLGRUNMACRO handler that powers the 'Run a Macro Multiple Times' dialog, so a tampered macro that is correctly blocked elsewhere still executes when invoked from that dialog. An attacker who can write to the current user's shortcuts.xml (for example later-stage malware, a tampered installer, or a low-integrity shared profile location) can plant a macro that calls internal Notepad++ commands, including commands that launch external programs, running entirely in that user's context with no privilege elevation. Exploitation is gated by local write access and by the victim opening the multi-run dialog; CVSS 3.1 rates it 6.7 (AV:L/AC:H/PR:L/UI:R), authentication requirements are authenticated for a local user per the provided vector (PR:L), and no public exploit identified at time of analysis. This is a genuine but low-urgency defense-bypass rather than a high-impact remote flaw.
Denial of service in Plone's Dexterity content system lets an authenticated user with content-creation rights submit items carrying excessively long titles, descriptions, or uploaded-file names, rendering the site unresponsive and leaving the resulting content hard to edit or delete. The flaw affects plone.app.dexterity through 3.2.2, 4.0.0-4.1.2 and 5.0.0, and plone.app.contenttypes through 3.0.11, 4.0.0-4.0.9 and 5.0.0, and carries a CVSS v3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) because the AV:N vector still requires a valid low-privileged account. At the time of analysis there is no public exploit code and no confirmed active exploitation (not in CISA KEV); the practical risk is highest on sites that permit open self-registration or grant content-editing permissions broadly to untrusted users, while the patched releases strictly cap field lengths.
Authenticated path traversal in MCP Atlassian (mcp-atlassian) prior to 0.22.0 lets a permitted MCP caller supply an absolute or traversal-laden file_path to the Confluence attachment-upload flow and cause the server to read and upload an arbitrary local file using the operator's credentials, exposing file contents to the linked Confluence instance. The flaw is a direct gap left by the CVE-2026-27825 fix, which hardened download destinations but never constrained upload source paths; only confidentiality is affected (no write or availability impact), and exploitation is bounded to files readable by the server process. No public exploit identified at time of analysis, and the issue is fully resolved by upgrading to 0.22.0.
Path traversal in MCP Atlassian (mcp-atlassian) before 0.22.0 allows an MCP caller that already holds attachment-upload authorization to supply an absolute path or ../ sequence to upload_attachment, causing the server to read an arbitrary server-local file and exfiltrate it through a Jira or Confluence attachment upload. The flaw is authenticated (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) and confidentiality-only: the resolved path is never confined to the server workspace, but there is no write, code-execution, or availability impact through this specific issue. No KEV listing and no public exploit code were identified at time of analysis, and the practical risk is bounded by the requirement that the caller is already trusted to invoke attachment tooling - highest in shared-credential or multi-tenant MCP deployments where the caller should not have host filesystem visibility. The vendor-released fix is version 0.22.0.
Path traversal in the MCP Atlassian MCP server (all versions prior to 0.22.0) allows an authenticated MCP caller that is authorized to invoke the Jira or Confluence attachment-upload tools to read arbitrary files as the server process. The upload tools accept a caller-supplied file_path and, before the fix, only normalised it with os.path.abspath without confining it to a workspace, so any path readable by the server account - tokens, keys, configuration - can be packaged and exfiltrated to an Atlassian issue or page; CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) reflects high confidentiality loss but no integrity or availability impact, and no public exploit code has been identified at time of analysis. The issue matters most in shared-credential or multi-tenant deployments, where a low-privilege caller gains read access far beyond its intended Atlassian scope.
Approval workflow gating in Nautobot 3.0.0 through 3.1.7 can be bypassed by an authenticated user who holds only the extras.add_approvalworkflowstageresponse permission. The generic REST API create endpoint for ApprovalWorkflowStageResponse omits the approver-group membership check, the change permission on the object under review, and the one-response-per-user restriction that the intended approve/deny actions enforce, and it exposes writable user and state fields so a response can be attributed to an arbitrary user. An attacker can therefore post forged "approved" responses, satisfy min_approvers, approve the workflow, and activate its gated ScheduledJob without any legitimate approver - a moderate-severity authorization flaw (CVSS 6.4, CWE-285) whose real-world risk is bounded by the requirement for an insider or compromised account that has been granted that specific add permission on an instance that actually uses approval workflows; no public exploit code was identified at time of analysis, and the vendor released a patch in version 3.1.8.
Concurrent HTTP requests to Traefik's BasicAuth middleware can reveal whether a username is configured, because absent usernames are collapsed into a single deduplicated (singleflight) computation while real usernames each trigger a separate password hash - a measurable timing discrepancy that unauthenticated, remote attackers can exploit. Only Traefik 3.6.11 through 3.7.12 are affected, and only when BasicAuth middleware is enabled; Traefik v2 and Digest authentication are explicitly unaffected. The issue discloses username existence only - no credentials are exposed and authentication is not bypassed - and no public exploit code or confirmed active exploitation was identified at time of analysis, with exploitation further gated on the attacker issuing timed concurrent requests and statistically distinguishing the two code paths (CVSS 4.0 AT:P). Patched in 3.7.13.
Reflected cross-site scripting in MCP Atlassian versions prior to 0.22.0 lets unauthenticated remote attackers inject markup or script through the OAuth error query parameter, which the CallbackHandler._send_response method in oauth_setup.py interpolates into an HTML page without escaping (CWE-79). Exploitation requires a deployment that uses the interactive OAuth setup flow and a targeted user who is actively completing that flow and opens the attacker's crafted authorization callback, which is why the assessed impact is confined to the victim's browser context (CVSS 5.4, C:L/I:L, UI:R) with no server-side code execution or Atlassian data-plane access. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the issue is fixed in version 0.22.0.
Plaintext storage of Atlassian OAuth credentials in MCP Atlassian before 0.22.0 lets any local user or process that can read the persisted token file recover live access and refresh tokens and reuse them against Confluence and Jira. The vulnerable code path is OAuthConfig._save_tokens, which writes ~/.mcp-atlassian/oauth-<client_id>.json using process-default permissions; on a host with a permissive umask, same-group or other local accounts can read it. Exploitation requires a pre-existing local foothold, a permissive umask, and that the OAuth plaintext-fallback file was actually created - it is not remotely exploitable and is not exposed on single-user hosts with a restrictive umask; no public exploit code was identified at time of analysis and this CVE is not in CISA KEV.
Password recovery via a timing oracle in LightRAG's /login endpoint lets remote, unauthenticated attackers (CVSS PR:N/UI:N) reconstruct plaintext AUTH_ACCOUNTS passwords one character at a time by measuring microsecond-scale response-time differences in Python's short-circuiting '==' comparison, but only in deployments that store credentials as plaintext rather than bcrypt-prefixed values. The attack requires high attack complexity (AC:H) - low-latency network positioning, many samples to overcome jitter, and credentials short or simple enough to recover before noise or rate limiting defeats the oracle. It is fixed in v1.5.5, which also introduces uniform bcrypt timing and login rate limiting; no public exploit code was identified at time of analysis.
Authenticated project administrators in Gardener can escalate their own project privileges by adding Group or ServiceAccount subjects to Project.spec.members, because the customverbauthorizer admission plugin's manage-members check only diffs User subjects and ignores Group and ServiceAccount entries. An actor holding the project-admin role but deliberately denied the manage-members permission can add the system:authenticated Group or an arbitrary ServiceAccount and thereby grant broad project access, including to Shoots, Secrets, and cloud provider credentials. All Gardener releases prior to 1.142.6, 1.143.3, 1.144.2, and 1.145.0 are affected; there is no public exploit code identified at time of analysis, and the issue is fixed in the versions listed above.
Denial of service and loss of unsaved work in Notepad++ versions prior to 8.9.8: a local process running at the same or a higher Windows integrity level on the same interactive desktop can send the NPPM_SAVESESSION window message with a null lParam, causing an immediate null-pointer dereference and termination of the editor. The flaw is rated CVSS 3.1 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning it requires a local low-privileged attacker process already present on the desktop, with no network vector, no user interaction, and impact limited to availability - no confidentiality or integrity compromise. Proof-of-concept level exploitation is indicated by SSVC (Exploitation: poc), and publicly available exploit code exists, but the issue is not confirmed as actively exploited in CISA KEV; the vendor-released patch is version 8.9.8.
Local credential disclosure in MCP Atlassian (sooperset/mcp-atlassian) prior to 0.22.0 allows a co-resident local user or process to read stored Atlassian OAuth access and refresh tokens and reuse the associated Atlassian session. The server creates its ~/.mcp-atlassian directory and the oauth-<client_id>.json token file without explicit owner-only permission modes (CWE-732), so the resulting group- or world-readable bits - an artifact of a permissive process umask - expose the tokens to anyone with read access on the host; the CVSS vector (AV:L/PR:L) confirms this requires an existing local account and no network reachability. Only multi-user or multi-process hosts that rely on the OAuth token-file fallback are exposed; single-user hosts with a restrictive umask are not. No public exploit identified at time of analysis, and the vendor CVSS of 5.5 understates impact only marginally - the independent assessment adds a low integrity component (I:L) because a stolen refresh token can also be used to act within the victim's Atlassian tenant. The issue is fixed in version 0.22.0.
Server-side request forgery in changedetection.io's Add Watch preview endpoint (/add_watch_ui/snapshot) allows remote attackers to force the server's browser fetcher to request attacker-chosen http(s) URLs, including loopback services, RFC1918 hosts, and the 169.254.169.254 cloud metadata address, because the url argument is validated only for an http:// or https:// prefix. The route is wrapped in login_optionally_required, so it can be reached unauthenticated on default installs that have no password set and requires credentials only where an operator has configured one; publicly available exploit code exists, and it is not confirmed as actively exploited (no CISA KEV entry). This is a moderate, credible risk rather than a critical one, with impact bounded to what the returned screenshot and rendered page data expose about internal targets; the vendor-released fix is version 0.60.1 (commit 71d332d5a0d3da2a0fe89a392413bf4b7d27c84e).
changedetection.io through 0.60.7 contains a timing side-channel in the check_authentication function of its Flask authentication hook, allowing unauthenticated remote attackers to potentially recover the application password by analyzing response-time differences. Exploitation is practically limited: it requires sending many requests and performing statistical analysis, and success is degraded by network latency, making it a low-to-moderate priority; a public proof-of-concept exploit exists, and the vendor did not respond to the disclosure.
Stored cross-site scripting in Nautobot (all versions prior to 2.4.37 on the 2.x branch and prior to 3.1.8 on the 3.x branch) lets an authenticated user with extras.add_relationship or extras.change_relationship permission inject HTML or JavaScript into a Relationship description, or with dcim.add_modulefamily or dcim.change_modulefamily permission inject it into a Module Family name, which then executes in the browser session of any user - including administrators and superusers - who opens an affected create or edit form. Because the payload runs in the victim's authenticated context with same-site access to the Nautobot UI, an attacker can perform actions as the victim and potentially steal session cookies or API tokens, enabling lateral movement and privilege escalation toward a full administrative compromise of the platform. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), so risk is assessed as moderate rather than critical: exploitation requires a pre-existing authorized account with specific object-level write permissions, and a higher-privileged victim must interact with the poisoned form.
Server-side request forgery in the Home Assistant IPP integration allows an attacker on the same local network to coerce the platform's shared HTTP client into issuing requests to loopback or other internal services, affecting Home Assistant Core versions prior to 2026.2.3. The attacker needs only to broadcast a crafted unauthenticated _ipp._tcp.local mDNS announcement whose host, port, and base_path values are consumed by async_step_zeroconf in homeassistant/components/ipp/config_flow.py, which then hands them to validate_input for printer metadata retrieval; the shared aiohttp client followed cross-origin redirects without blocking loopback targets, so no prior IPP configuration, no authentication (PR:N), and no user interaction (UI:N) are required. Impact is bounded by the adjacent-network vector (AV:A) and by the constrained confidentiality and integrity effects of the coerced internal request - no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); exploitation conditions are local-network only, not internet-reachable. Fixed in 2026.2.3.
Server-side request forgery in MCP Atlassian (sooperset/mcp-atlassian) prior to 0.22.0 lets an MCP caller who controls the public Jira base URL have a Jira user-lookup request redirected to an internal address, bypassing the SSRF redirect protections previously added for CVE-2026-27826. The vulnerable path is JiraUserMixin._lookup_user_by_permissions, which calls the module-level requests.get instead of the fetcher's protected session, so the response hook that enforces redirect validation is never applied. Impact is limited and blind (confidentiality-only, no integrity or availability effect) and, per the independent assessment, requires the attacker to control the Jira endpoint plus a server that issues a redirect to an internal target, making it most realistic in HTTP/multi-user or shared-credential deployments rather than single-user stdio setups with a fixed trusted Jira URL. No public exploit code was identified at time of analysis and there is no KEV listing; v0.22.0 resolves the issue.
Authenticated users of Unleash (npm unleash-server) prior to 8.0.3 who hold create or clone rights in any single project can abuse the clone-feature endpoint to copy a feature toggle out of a different project they cannot read, then inspect the copied strategy parameters, constraints, variants, and variant payloads. The flaw is a broken object-level authorization (CWE-639) in cloneFeatureToggle and POST /api/admin/projects/:projectId/features/:featureName/clone: the destination project is authorized but the source project is never checked, and because feature names are globally unique an attacker only needs the target feature's name (which may leak through SDKs shared across projects). Impact is limited to information disclosure (CVSS 4.0 5.3, PR:L, no integrity or availability effect); the vendor fixed it in 8.0.3 and no public exploit or CISA KEV entry was identified at time of analysis.
Reflected cross-site scripting (CWE-79) in ClipBucket v5 before 5.5.3-#182 allows unauthenticated remote attackers to inject and execute arbitrary JavaScript in a victim's browser under the application origin by crafting URLs whose cat, sort, or time query parameters are processed by the unsanitized sort_link() helper. Exploitation requires the victim to click a crafted link (user interaction), public exploit code is available, and there is no indication of confirmed active exploitation (no CISA KEV listing); impact is confined to the victim's browser session rather than server-side code execution.
Improper restriction of excessive authentication attempts (CWE-307) in the 9Router AI router package (decolua/9router) before version 0.5.6 allows remote unauthenticated attackers to defeat the dashboard login lockout by rotating the client-controlled X-9r-Real-Ip header on every password guess, so each request lands in a fresh failed-attempt bucket and the five-attempt progressive 429 lockout never fires. The flaw is exploitable only in deployments where HTTP requests reach Next.js directly without the bundled custom-server.js wrapper that normally overwrites X-9r-Real-Ip from the unspoofable TCP socket address; the login endpoint binds to 0.0.0.0 by default, so exposure is network-reachable. Impact is limited to confidentiality (unauthorized administrative session only if the dashboard password is separately weak or guessable) and the throttle removal itself does not yield credentials; no public exploit identified at time of analysis, and the weakness is not listed in CISA KEV.
Stored cross-site scripting in Novu's in-app notification inbox (all versions prior to 3.18.0) allows an authenticated organization member or an environment API-key holder to persist a javascript:-scheme redirect URL in an in-app workflow call-to-action, which is then executed via window.open in the inbox-hosting origin when a recipient clicks the notification. Exploitation requires both the low-privilege write access described above (CVSS 4.0 PR:L, assessed CVSS 3.1 PR:L) and victim interaction in a Chromium-based browser (UI:P), limiting reliable impact to confidentiality and integrity of the embedding customer application or self-hosted Novu dashboard rather than the Novu platform itself. The issue is fixed in version 3.18.0; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated users who hold the UPDATE_FEATURE_STRATEGY permission in any single project can reorder the activation strategies of features in other projects, features, or environments in Unleash prior to 8.0.3, because the set-sort-order endpoint authorizes only against the project ID in the URL and then writes strategy IDs taken from the request body by primary key without verifying they belong to that context. In multi-project Pro or Enterprise deployments this is a cross-project integrity write that can flip which activation strategy takes precedence for another team's flag in production and is recorded under the attacker's own project context, while the single-project OSS edition is still affected but limited to unauthorized reordering across features or environments within the default project. The assessed severity is low (CVSS 3.1 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) - it requires a valid project role and knowledge of victim strategy IDs, and the impact ceiling is only sort_order changes, since strategy parameters, constraints, and segments cannot be altered; no public exploit identified at time of analysis.
Reflected cross-site scripting in Autonomy Logic OpenPLC 3 (OpenPLC Runtime) lets a remote, unauthenticated attacker craft a URL whose routing query-string parameter carries script payload that is reflected into the page without encoding, executing in the browser of any operator who clicks the link while holding an active web-management session. Exploitation is entirely dependent on social engineering of a legitimate operator (UI:R per CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, base 6.1) and the web interface must be network-reachable to that operator. No public exploit code was identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); impact is confined to the victim's browser session and same-origin web context, with no direct compromise of the PLC runtime or loss of availability.
An off-by-one error in the RTI Connext Professional Core Libraries (CWE-193) produces an out-of-bounds write that can overflow a buffer when a crafted DDS/RTPS message is parsed, affecting Connext Professional 7.4.0 up to (but not including) 7.7.0.1 and 7.0.0 up to (but not including) 7.3.1.6. Per the CVSS 4.0 vector the flaw is remotely reachable over the network with low complexity and requires no authentication and no user interaction, but impact is bounded: there is no confidentiality loss (VC:N) and only partial integrity and availability impact (VI:L/VA:L), giving a medium-severity 6.9 rather than a code-execution-class outcome. There is no public exploit identified at time of analysis and the issue is not in CISA KEV; practical exposure is further limited because DDS middleware is normally deployed on segmented operational networks in robotics, autonomous systems, and aerospace/defense environments rather than being directly internet-facing.
Double free in the Core Libraries of RTI Connext Professional 7.4.0 to 7.7.0.0 and 7.1.0 to 7.3.1.5 allows a local authenticated attacker to manipulate files and cause denial of service. The issue requires local access and low-level privileges, is not remotely reachable, and no public exploit code has been identified. Patches are available in versions 7.7.0.1 and 7.3.1.6.
MISP's pre-authentication TOTP login path can reveal that a disabled account is TOTP-enrolled because the database query omits User.disabled, causing the disabled-account check to evaluate as false and present a TOTP prompt instead of an immediate rejection. This affects unauthenticated remote attackers who can reach UsersController::login(), but no authenticated access is granted because the downstream identify() call re-validates and rejects the disabled account. The practical impact is negligible: a small login-response information leak and a PHP undefined-array-key warning; no public exploit was identified at time of analysis, and the independent assessment rates the issue as low confidentiality impact only.
Blind server-side request forgery in MISP allows unauthenticated remote attackers to coerce the MISP server into making outbound HTTPS requests to arbitrary internal or external targets by POSTing a crafted XML body containing a bare HTTPS URL to the unauthenticated cspReport endpoint. The flaw arises because PHP operator precedence in Xml::build()'s readFile guard (`readFile && http || https`) leaves the HTTPS locator fetch path ungated, and RequestHandlerComponent automatically decodes XML request bodies on write requests. Exploitation is constrained to blind SSRF with no response body returned to the attacker, so it primarily enables probing, timing-based reconnaissance, and triggering GET-style actions on reachable HTTPS services; no public exploit code was identified at time of analysis, and a vendor patch commit is available.
Unrestricted file upload in JosephChuks php-file-manager-with-code-editor through 3.0 lets an attacker with low privileges upload arbitrary files via the move_uploaded_file call in filemanager.php, potentially achieving PHP code execution if the uploaded file lands in a web-executable directory. The flaw is CWE-434 and carries an upstream CVSS 4.0 score of 6.9, while the independent CVSS 3.1 assessment rates PR:L with high confidentiality/integrity/availability impact and cautions that reachability without authentication and final execution location are unconfirmed. No public exploit code has been identified, and the vendor did not respond to disclosure.
MISP installer scripts for Debian 12/13, Ubuntu 24.04, and RHEL 9.4 write all installation output - including the generated admin password, database passwords, GPG passphrase, and supervisor password - into /var/log/misp_install.log, which is created world-readable (typically 0644) under the system default umask, with a companion world-readable FIFO at /var/log/misp_install.log.pipe. Any local unprivileged user on the host can read these credentials, and because the log persists after installation, the exposure is durable rather than limited to the install window; a pre-existing symlink in /var/log could also have redirected the write to an arbitrary location since the file was not removed before creation. The flaw affects MISP versions below 2.5.47 and requires a local account on a machine where an administrator has run one of the affected installer scripts; no public exploit code was identified at time of analysis. A vendor patch is available via upstream commit d5d72ab38, which forces root-only 0600 permissions on both the log and the FIFO.
Cross-site request forgery in MISP (Malware Information Sharing Platform) before v2.5.47 lets an unauthenticated attacker cause an authenticated administrator's browser to execute arbitrary workflow modules on the victim instance. Because the WorkflowsController's moduleStatelessExecution action was listed in CakePHP's unlockedActions, both the CSRF token check and the form field-hash validation were disabled, so an attacker-crafted cross-site form post submitted by a logged-in admin runs a module's exec() method with attacker-chosen input and parameters - including action modules that write blocklist and warninglist entries. The result is a high-integrity, low-complexity compromise of security-relevant data with no confidentiality or availability impact, and no public exploit code identified at time of analysis; this is a genuine but moderate-priority integrity flaw rather than an inflated high-CVSS finding, requiring the victim admin to be authenticated and induced to submit the crafted request.
Authentication bypass in the Keycloak (Red Hat Build of Keycloak) Kerberos federation provider lets an attacker on the same or adjacent network impersonate the Key Distribution Center and bypass Kerberos password authentication, potentially gaining unauthorized access to user accounts. The flaw only manifests in the specific, non-default configuration where Kerberos PASSWORD authentication is used while SPNEGO is disabled, because that mode never requests a server ticket to verify the KDC's identity. Rated CVSS 3.1 6.8 (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), exploitation requires network adjacency and an active on-path spoofing operation; no public exploit code has been identified and the CVE has not been listed as confirmed actively exploited (CISA KEV).
Out-of-bounds read in the Core Libraries of RTI Connext Professional allows a locally positioned attacker with low-level privileges on a host running the middleware to trigger an overread that can crash or destabilize the affected process, producing a denial-of-service condition. Affected builds span 7.4.0 before 7.7.0.1, 7.0.0 before 7.3.1.6, and the 6.1.x, 6.0.x, 5.3.x, 5.2.x and 5.0.0-5.1.x branches; systems already on the fixed builds are not exposed. The impact is availability-only with no confidentiality or integrity effect, and because the attack requires local access and valid credentials rather than network reachability, realistic exposure is limited to insider or already-foothold scenarios causing service disruption. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Out-of-bounds reads in the Core Libraries of RTI Connext Professional can be triggered by local attackers who already hold low-privilege access to a host running the RTI Connext data bus, causing the middleware process to crash and disrupting availability. The flaw affects Connext Professional versions 7.4.0 through 7.7.0.0, 7.3.0 through 7.3.1.5, and 6.1.2.21 onward within the 6.1.* line, and stems from a combination of type confusion, a function called with an incorrect number of arguments, and resulting buffer over-reads in the Core Libraries. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), and because exploitation requires local access plus valid low-privilege credentials while the sole impact is a process crash, the realistic priority is low-to-medium rather than matching the raw 6.8 CVSS 4.0 base score.
An out-of-bounds read combined with type confusion in the Core Libraries of RTI Connext Professional (versions 7.4.0 before 7.7.0.1, and 7.3.0 before 7.3.1.6) lets a local attacker with low privileges feed a crafted malformed data type or message that the library misinterprets, producing buffer overreads and a high-availability impact such as a crash of the affected process. The vendor's CVSS 4.0 vector (6.8, MEDIUM: AV:L/AC:L/AT:N/PR:L/UI:N, VC:N/VI:N/VA:H) describes a strictly availability-impacting flaw with no confidentiality or integrity compromise claimed, and the independently assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) agrees. Exploitation requires local access to the host running the Core Libraries rather than remote reach into a DDS domain, and at time of analysis no public exploit code or confirmed active exploitation was identified.
Downgrade attacks against the Tauri updater plugin (tauri-plugin-updater) 2.8.0 through 2.11.x are possible because the plugin's `check` IPC command accepts an `allowDowngrades` boolean directly from frontend JavaScript, letting any code running in the app webview flip the version check from "update must be newer" to "update must be different." Where the default permission set grants allow-check to the webview, an attacker who already has an XSS foothold in the application frontend can invoke this command unauthenticated and, if they also control or compromise the update endpoint to serve an older but still validly signed release, force the app to roll back to a vulnerable version. Exploitation is conditional - it requires a pre-existing XSS, the default permission set, no custom Rust-side version comparator, and influence over the update feed - and carries a user-interaction requirement (UI:R); no public exploit code has been identified at time of analysis and the flaw is not in CISA KEV. The practical impact is an integrity and access-control failure (our assessment scores it C:N/I:H/A:N) rather than a confidentiality compromise.
Session fixation in web.py 0.76 allows a remote attacker who can plant a known session_id in a victim's browser cookie to inherit that victim's authenticated session, because the built-in Session component never regenerates the identifier after login. The flaw is unauthenticated from the attacker's perspective (PR:N) but requires user interaction (UI:R) and a working cookie-fixation vector (AC:H), yielding a CVSS 3.1 base score of 6.8 with high confidentiality and integrity impact scoped to the individual victim's account rather than the server. No public exploit code and no confirmed active exploitation were identified at time of analysis; impact is limited to web.py 0.76 applications that use the framework's native Session handling for authenticated sessions.
Improper input validation in Adobe CAI Content Credentials (the Rust SDK and the command-line tool) lets remote, unauthenticated attackers bypass integrity protections and gain unauthorized write access to Content Credentials data when a victim processes attacker-controlled content - a maliciously crafted URL or a compromised web page. Affected organizations are those embedding the Content Credentials Rust SDK or running the command-line tool in content pipelines; the impact is limited to integrity (C:N/I:H/A:N), meaning tampered provenance/manifest data rather than data theft, denial of service, or code execution. No public exploit identified at time of analysis and the issue is not reported as actively exploited; Adobe has published advisory APSB26-147, so patched builds should be applied as routine hygiene.
Information disclosure in LibreOffice allows a crafted document containing hyperlinks to cause local environment-variable and INI-file values to be expanded into the URL and exfiltrated to a remote server when the victim opens the file. The flaw is an incomplete fix for CVE-2024-12426: the earlier guard matched only some ways of naming the package content provider, so a URL naming it differently still reached the expansion logic, whereas fixed builds match the provider during URL checking. Exploitation requires the victim to open an attacker-supplied document (UI:R / UI:P) on the local attack vector, there is no public exploit identified at time of analysis, and the primary impact is confidentiality only (no integrity or availability loss).
Cross-environment integration tampering in Novu before 3.18.0 lets an authenticated caller who holds an environment-scoped API key or a dashboard (JWT) session for one environment act on an integration that belongs to a different environment within the same organization, deleting it, rewriting its provider credentials, promoting it to primary, or triggering auto-configuration by supplying the target environment's integrationId. The advisory-defined scope covers both environment API keys and dashboard sessions, but the v3.18.0 release closes only the environment-scoped API-key path (HTTP 403, 'is scoped to a single environment') while its own tests deliberately preserve cross-environment dashboard-session behavior, so 3.18.0 is a partial remediation and installations at or above that version remain exposed through the JWT/dashboard vector. Severity is moderate (CVSS 6.5, CWE-639): integrity and availability are fully impacted while confidentiality is not, no cross-organization access is possible, exploitation requires existing authenticated access plus knowledge or enumeration of a target integrationId, and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Denial of service in the Python icalendar library (versions 6.1.0 through 7.2.1) allows unauthenticated attackers to exhaust CPU and heap memory by supplying iCalendar content whose VALARM REPEAT property carries an extremely large value. Parsing the file is harmless on its own; the resource exhaustion fires only when an application then reads alarm-expansion properties such as Alarms.times, Alarms.active (affected since 6.1.0) or Alarm.triggers (affected since 7.0.0), which eagerly materialize the repeated alarm occurrences because no application-level cap existed before the fix. The assessed CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so the sole impact is availability - this is a CWE-400 resource-exhaustion flaw, not code execution or data compromise, and no public exploit code was identified at time of analysis. Vendor-released patch: 7.2.2.
A denial of service in Netdata Agent versions prior to 2.10.4 lets an authenticated streaming child agent crash the parent Netdata agent that collects its metrics, repeatedly disabling centralized monitoring. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5), the attacker must already be an accepted child in the parent-child streaming topology and then sends an oversized CHART SLOT value in the plugins.d streaming protocol; the parent parses it as a chart-cache index, attempts an approximately 16 GiB allocation for the chart-pointer array, fails, and aborts via fatal(). There is no confidentiality or integrity impact, and no public exploit code has been identified at time of analysis (the vulnerability is not in CISA KEV); the real risk is bounded and operational, concentrated in deployments that accept streaming children and in multitenant or partially trusted streaming setups.
An authenticated Netdata child agent can crash its parent agent by streaming an oversized DIMENSION SLOT value in the plugins.d protocol, triggering an integer overflow that leads to a heap out-of-bounds write and termination of the parent process. Affected deployments are Netdata parent-child streaming setups running versions prior to 2.10.4 (including nightly builds earlier than 2.10.0-782-nightly); the attacker must already control or have compromised a child agent that is authenticated to the parent, so exploitation is limited to denial of service with no confidentiality or integrity impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV; risk is moderate rather than urgent, and it is fully closed by upgrading to the fixed release.
Arbitrary file read in BM Content Builder plugin for WordPress versions before 3.17.1 allows authenticated attackers with at least Subscriber-level access to read the contents of files on the server. The flaw is a directory traversal issue in the ux_cb_page_customize_save_layout_ajax() AJAX handler, and it requires only an authenticated request, with no additional user interaction. No public exploit code was identified at time of analysis, and the impact is confidentiality-only, making this a moderate-priority authenticated vulnerability rather than an actively exploited one.
Denial of service in NVIDIA Infrastructure Controller for Linux affects versions 0 through 1.9, where an attacker who already holds valid low-privilege credentials on the controller can trigger uncontrolled resource consumption that degrades or halts the service (CWE-400). The CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) reflects a remotely reachable flaw with low attack complexity and no user interaction, but impact is confined to availability - there is no data disclosure or modification. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit identified at time of analysis, so real-world risk is bounded primarily by the requirement for authenticated access to the controller.
Denial of service in NVIDIA Infrastructure Controller for Linux (versions 0 through 1.9) lets an authenticated, low-privileged user with network reach to the management interface exhaust resources and degrade or halt the controller. The flaw is a CWE-400 uncontrolled resource consumption issue rated vendor CVSS 3.1 base 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), meaning availability-only impact, no confidentiality or integrity loss, low attack complexity, and no user interaction, with the credential requirement being the principal barrier to exploitation. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, no EPSS score was provided, and the exact triggering request or feature is not disclosed in the vendor description.
Unauthenticated writes to the Netdata settings store are possible in versions 2.0.0 through 2.10.x because the /api/v3/settings endpoint was registered with HTTP_ACL_NOCHECK and HTTP_ACCESS_ANONYMOUS_DATA, letting remote callers send PUT requests that bypass the operator-configured 'allow dashboard from' IP allowlist. An attacker with network reachability to the agent's HTTP/dashboard listener (default TCP 19999) can persist attacker-controlled JSON into {varlib}/settings/default.json, tamper with its version counter, and repeatedly push near-20 MiB payloads to exhaust disk space, though the file does not govern data collection or security policy. Impact is capped at low integrity and low availability (CVSS 3.1 base 6.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L); no public exploit code was identified at time of analysis and there is no evidence of confirmed active exploitation. The issue is fixed in Netdata 2.11.0.