Credential leak in the GDevelop desktop app through 5.6.284 allows unauthenticated remote attackers to exfiltrate a victim's gd_resource cloud session cookie by embedding an attacker-controlled resource URL in a crafted project file, which downloadLocalFile() requests with the cookie attached regardless of destination host; this exposes private GDevelop cloud project resources. Exploitation requires the victim to open the malicious project while holding an active GDevelop cloud session, so impact is limited to confidentiality (CVSS 4.0 base 5.3, medium; independent assessment CVSS 3.1 5.3, UI:R). No public exploit code or CISA KEV entry was identified in the provided intelligence at time of analysis.
Authenticated Teacher-role users can modify course content they do not own in Sensei LMS before 4.26.4 by abusing the add_new_module_term AJAX handler, which validates only a generic nonce rather than per-course edit permissions. Attackers can reuse a nonce from their own course metabox to call wp_set_object_terms against arbitrary course IDs, enabling unauthorized assignment of module taxonomy terms on courses owned by other teachers or administrators. No public exploit code has been identified at time of analysis; impact is integrity-only and most meaningful on multi-author sites, while single-instructor deployments have negligible exposure.
Authenticated customers on Thelia e-commerce stores can bypass coupon usage limits by exploiting order-payment timing, allowing them to obtain discounts beyond a coupon's configured cap. The flaw affects Thelia before 3.1.5 and 3.2.x before 3.2.4, requires a valid customer account plus a usage-limited coupon and a pay-later or cancellation workflow, and carries a moderate CVSS 4.0 score of 5.3 with integrity-only impact; no public exploit identified at time of analysis.
Frappe CRM before 1.74.0 allows authenticated Sales Users to attach attacker-written notes and tasks to other users' call logs, leads, and deals by supplying arbitrary call_sid values to the add_note_to_call_log and add_task_to_call_log endpoints. The endpoints lack a frappe.has_permission('CRM Call Log', 'write', ...) ownership check, so impact is limited to integrity of annotations-no confidentiality or availability effect-and exploitation requires a valid Sales User session rather than anonymous access. Vendor patches are available in v1.74.0; no public exploit identified at time of analysis.
Frappe CRM before 1.81.2 allows authenticated Sales Users to read, mark read, or delete other users' CRM Notification records by querying the frappe.client endpoints with a to_user filter or by passing a victim's user argument to the mark_as_read API. The missing-authorization flaw (CWE-862) exists because the CRM Notification doctype defines no permission query conditions or has_permission hook and the API trusted a caller-supplied user value; System Manager and Administrator accounts are exempt, and impact is confined to notification records rather than core CRM data. Rated medium severity (CVSS 5.3), it requires an authenticated Sales User account and works against default configurations; no public exploit code or confirmed active exploitation was identified at time of analysis, and vendor-released patch 1.81.2 is available.
Server-side request forgery in KitchenOwl through 0.7.10 lets an authenticated household member abuse the recipe-import feature to make the backend fetch attacker-influenced URLs a second time without IP filtering, potentially reaching loopback, private-network, or cloud-metadata services and reading their responses. The attacker must host a publicly reachable page titled "KitchenOwl" whose path matches /recipe/<id> so that local-instance detection fires and the follow-up requests.get() runs outside the hardened client. Impact is limited to information disclosure from internal services reachable by the server (no write, no code execution), and exploitation requires a valid household account; no public exploit code was identified at time of analysis and the issue is not in CISA KEV.
Missing authorization in YITH WooCommerce Product Bundles through 2.29.0 lets unauthenticated remote attackers invoke access-controlled plugin functionality and perform a limited, low-integrity action on WordPress/WooCommerce sites running the plugin. The CVSS 3.1 score is 5.3 (AV:N/AC:L/PR:N/UI:N) with no confidentiality or availability impact; no public exploit was identified at time of analysis, and there is no CISA KEV entry.
Missing authorization in the FluentForm WordPress plugin through 6.2.15 allows unauthenticated remote attackers to perform an integrity-impacting state-changing action without proper access-control checks (CVSS 5.3, CWE-862). The vulnerability affects sites running FluentForm at or below 6.2.15 and is bounded to integrity-only impact, with no confidentiality or availability loss per the assessed vector. No public exploit code or CISA KEV entry was identified at time of analysis, and no EPSS score was provided.
Missing authorization (CWE-862) in the VideoWhisper Broadcast Live Video WordPress plugin through version 7.3.7 allows unauthenticated, remote attackers to reach plugin functionality that should be access-controlled, exposing limited confidential data or restricted operations (CVSS 3.1 score 5.3, confidentiality-only). Default installations are exposed because the CVSS vector is PR:N/UI:N, but no public exploit code was identified at time of analysis and there is no CISA KEV confirmation of active exploitation. No vendor-released patch version is identified in the available data.
Error responses from the Apache Camel gRPC consumer component can leak internal exception details to remote callers: when a route behind a gRPC consumer fails, the exception's message is copied into the gRPC status description, which is transmitted back across the wire rather than kept server-side like the status cause. Unauthenticated remote callers who can provoke a route failure on an affected deployment (Camel 4.0.0 before 4.18.5, or 4.19.0 before 4.22.1) may read class and package names, filesystem paths, host names and connection detail embedded in those messages, at CVSS 5.3 with confidential-impact-only. The leak is conditional on the exception text itself carrying sensitive content and on the gRPC consumer being reachable, so real-world exposure varies by route; there is no public exploit identified at time of analysis and no confirmed active exploitation. Vendor patches are published (4.23.0, plus LTS 4.18.5 and 4.22.1), and the fixed builds default a new muteException option to true so patched deployments stop leaking unless they explicitly opt out.
Apache Camel's CXF component leaks internal deployment detail back to SOAP clients when a route behind a CXF SOAP consumer fails with an exception that the service contract does not declare - CXF copies the exception message into the SOAP faultstring and, when configured to do so, the stack trace into the fault detail. Deployments running Camel 4.0.0 through 4.18.4 or 4.19.0 through 4.22.0 with an exposed CXF SOAP consumer are affected; an external caller who can provoke an undeclared failure can read class and package names and whatever the exception message carries, at CVSS 3.1 base 5.3 (AV:N/AC:L/PR:N/UI:N/C:L/I:N/A:N, CWE-209). Declared @WebFault exceptions are intentionally unaffected because they are part of the published contract. No public exploit code has been identified at time of analysis, and the issue is a read-only disclosure rather than code execution or data modification.
Error messages written back over the socket by the Apache Camel camel-mina consumer leak internal deployment details to any remote peer that can provoke a processing failure. Affected deployments are Camel 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0 that use camel-mina as a consumer (socket server) in sync mode, where the peer is unauthenticated per the CVSS vector (AV:N/AC:L/PR:N/UI:N) and the impact is limited to confidentiality (C:L) with no integrity or availability effect. The exposure ranges from exception class and message text under the textline codec to a fully serialised exception with its cause chain under the object codec; exploitability depends on the attacker reaching the socket and triggering a failure, and no public exploit code or confirmed active exploitation was identified at time of analysis - treat this as moderate-severity hardening rather than an urgent threat.
Apache Camel's camel-knative HTTP consumer writes the full exception - class name, message, and stack trace - back to the remote caller whenever an exchange fails on the consumer side, letting any external sender provoke a route failure and harvest internal deployment detail (package and class names, host names, file paths, route shape, and any configuration or connection strings embedded in exception messages). The flaw affects Camel from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1; camel-knative was the last HTTP-family consumer not yet aligned with the muteException behaviour introduced for the other HTTP consumers under CAMEL-23651. Rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N, C:L only), it requires the Knative HTTP consumer to be reachable by untrusted callers and an induced processing failure; no public exploit code was identified at time of analysis and there is no indication of active exploitation.
Authenticated MISP users who can read or edit server settings can obtain module-declared secrets and change settings that module authors intended to be CLI-only in versions before 2.5.48. The flaw is caused by server-side rebuilding of module settings for API use dropping the redacted and cli_only flags, affecting the servers/getSetting and servers/serverSettingsEdit endpoints; instances without enabled modules declaring those flags are not exposed. No public exploit identified at time of analysis, and the vendor has provided a patch commit (6c02f0f5c) with fixed versions at 2.5.48 or later.
MISP deployments before 2.5.48 leave orphaned child records behind when an event is deleted, so threat-intelligence metadata such as event report tags, event graph entries, proposal (shadow attribute) correlations, fuzzy ssdeep correlation chunks and attachment/malware-sample scan results persist in the database after the parent event is gone. Triggering the incomplete cleanup requires an authenticated user with event-deletion privileges (PR:H), and actual information exposure is further gated on those orphaned rows being reachable through other application queries or administrative interfaces that do not validate parent-event existence; the vendor vector accordingly scores only a low integrity impact with no confidentiality or availability impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the flaw is fixed upstream in commit 5f78634af, shipping in MISP 2.5.48.
Element X iOS releases before 26.05.0 parse io.element.call:// deep links without validating the embedded target against a URL allowlist, allowing a crafted link to load an attacker-controlled origin into the in-app call screen's WKWebView. Because that web view runs inside the Element X process, it inherits any microphone and camera permissions the user previously granted the app, so the attacker's page can reach device media capture. Exploitation requires the victim to actually open the malicious link and to have already granted Element X iOS media permissions; the vendor fixed the issue in 26.05.0, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Stored cross-site scripting in SourceCodester Inventory System 1.0 allows an authenticated user to inject script through the Hsn_Code parameter of /api/transactions_handler.php?action=save_sale, which executes in another user's browser when the saved sale is viewed. Exploitation requires an authenticated account and victim interaction, limiting real-world urgency; no public exploit identified at time of analysis and no CISA KEV active-exploitation signal was provided. The assessed impact is a limited integrity effect in the victim's browser context, with no confidentiality or availability impact.
Path traversal in GrandNode2 through 2.3.0 lets an authenticated administrator with access to the Excel product-import feature read files from the server by supplying local filesystem paths in the Picture1, Picture2, or Picture3 columns; the vulnerable code passes those values to file-read operations without http(s) or host validation. The issue is medium severity, high-privilege gated, and fixed in 2.4.0; no public exploit identified at time of analysis.
Address-bar spoofing in Sleipnir Mobile for Android before 3.9.0 lets attacker-controlled web pages paint a counterfeit trusted-origin address bar over their own content, because entering fullscreen through the HTML Fullscreen API fails to display the persistent fullscreen notification or trusted-origin indicator users depend on. The forged browser chrome can masquerade as a credential prompt, forced update, or payment page, so the realistic outcome is phishing-driven credential theft, malware delivery, or social-engineering fraud rather than direct code execution or data access. Exploitation is interaction-gated (the victim must open hostile content in this specific browser and complete a single tap), remote attackers need no authentication per the CVSS 4.0 vector, no public exploit code has been identified at time of analysis, and Fenrir has released 3.9.0 to correct the issue.
Stored cross-site scripting in Koalix CRM through 1.14.0 allows authenticated staff users who can create or edit tasks to persist HTML or JavaScript in a task title, which the Task.link_to_task() helper renders unescaped inside the Django admin task changelist and change form. The payload stays inert until an administrator views the affected list or record, so successful abuse requires admin interaction and, at minimum, a valid staff-level account - meaning the realistic threat is a malicious or compromised insider rather than an anonymous remote attacker. Impact is rated medium (CVSS 4.0 base 5.1; assessed CVSS 3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) and no public exploit code or confirmed active exploitation was identified at time of analysis; an attacker who does land the payload could perform admin-context actions such as creating a superuser account.
Frappe Helpdesk releases before 1.26.0 trust a client-supplied raised_by value in the hd_ticket.api.new endpoint, letting an authenticated low-privilege portal user create tickets that appear to originate from another customer's email address. Because that same identity field drives the ticket activity lookups, the attacker can also pull the victim's thread replies through get_ticket_activities, enabling targeted phishing planted directly inside the victim's support portal. Successful abuse requires a valid portal account and passive victim engagement with the fabricated ticket, and no public exploit code or active exploitation has been identified at time of analysis; the vendor-released patch is v1.26.0.
Cleartext storage of remote log server credentials, truststore passwords, and keystore passwords in WSO2 API Manager and related WSO2 products lets high-privileged authenticated Management Console users or anyone with direct read access to product files recover secrets when remote logging is enabled. The flaw is medium severity (CVSS 4.9, CWE-312) and limited to confidentiality; it can enable manipulation of log entries and compromise of the remote log server after credentials are obtained. No public exploit was identified at time of analysis, and deployments without remote logging enabled are not exposed through this path.
Stored cross-site scripting in GrandNode 2 through 2.3.0 lets a back-office operator with product-editing rights (store manager or vendor) plant script inside a product description that Grand.Web later renders unencoded through Html.Raw in Product.Layout.Simple.cshtml, so the payload executes in the browser of any other user who opens that product page. Because the CVSS vector carries PR:H, anonymous or unprivileged attackers cannot inject the payload themselves; the practical exposure is confined to deployments with multiple partially trusted operators, such as multi-vendor marketplaces, and execution still requires a victim to view the compromised page. A vendor fix is available in 2.4.0-beta and 2.4.0 (commit 41a8e349eab8d9641cf6ea800d738f2d8991ca22), no public exploit code has been identified at time of analysis, and this is best treated as a genuine but low-to-moderate priority flaw rather than an urgent threat.
Out-of-bounds read in libaribcaption 1.1.0 through 1.1.2 lets crafted ARIB STD-B24 captions drive DecoderImpl::HandleGLGR() past the 78-entry kLatinSpecialTable, leaking adjacent read-only data or crashing the decoder. The issue is local and requires the victim to process an attacker-supplied caption stream (UI:P, PR:N), with limited confidentiality and availability impact; no public exploit identified at time of analysis. It is fixed upstream in commit 9917cb3.
Apache Camel's camel-http OAuth2 client-credentials token cache is keyed only on the request URI, client ID and client secret, so two endpoints in the same JVM that differ solely in OAuth2 scope, resource indicator or token endpoint collide on one cache entry and one route can be served a token minted for another. Affected are Apache Camel 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0 with token caching enabled (oauth2CacheTokens=true) and at least two such OAuth2 endpoints configured; deployments with a single endpoint, or endpoints that also differ in URI or credentials, are not impacted. Rated CVSS 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, CWE-524), the practical consequence is authority confusion between the operator's own routes rather than an external attack path, and no public exploit identified at time of analysis; fixed in 4.23.0, 4.18.5 and 4.22.1.
Prefix confusion in Apache Camel's camel-platform-http component silently promotes ordinary HTTP endpoints to forwarding proxies, letting remote unauthenticated callers relay requests to targets they choose via the Host header and reach content the route author never intended to expose. Only Camel deployments running a platform-http route whose configured path begins with the five characters 'proxy' (for example proxyStats, proxy-health or proxying) while not intending the documented platform-http:proxy endpoint are affected - a developer-introduced naming condition that keeps attack complexity high and drives the modest CVSS 3.1 score of 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N). Default deployments without such endpoints are not exploitable, and no public exploit code or CISA KEV entry was identified at time of analysis.
Apache Camel 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0 let a remote sender choose which saga their exchange joins by supplying the unprefixed 'Long-Running-Action' header, because the saga processor consulted that header on every exchange rather than only for saga services that participate in an external LRA protocol. The consequence is limited to deployments running sagas through the camel-lra component with a real LRA coordinator and a consumer that accepts inbound messages from untrusted senders: an attacker can attach a request to a long-running action started by someone else, or force compensation to be associated with an action they did not initiate, yielding low confidentiality and integrity impact (CVSS 4.8, AC:H). Vendor-released patches exist in 4.23.0, 4.18.5 and 4.22.1, and no public exploit has been identified at time of analysis.
Apache Camel's camel-keycloak security processor can accept a token minted by an issuer other than the configured one when token introspection is in use, the opt-in issuer validation is enabled, and the introspection endpoint returns an active response that omits the 'iss' claim - the check was skipped instead of failing. The flaw affects Apache Camel releases from 4.15.0 up to but not including 4.18.5, and from 4.19.0 up to but not including 4.22.1, specifically deployments using the camel-keycloak component with token introspection. Exploitation is unauthenticated per the CVSS vector (PR:N) but demands a non-default chain - introspection enabled, validateIssuer explicitly turned on, and a broker/gateway/minimal introspection endpoint that omits iss and serves multiple issuers - which caps the score at 4.8; no public exploit identified at time of analysis, and vendor-released patches exist in 4.23.0, 4.18.5 and 4.22.1.
Reflected cross-site scripting in MISP workflow module configuration pages affects versions before 2.5.48 and allows an attacker who can influence the parameter names returned by the misp-modules service to inject HTML or JavaScript into form labels viewed by an authenticated MISP user. Exploitation requires influence over the module service plus a victim who actively opens the affected workflow module page, so a crafted link alone is insufficient; the issue is medium severity (CVSS 4.0 base 4.8) and no public exploit was identified at time of analysis. MISP 2.5.48 encodes the generated label with h() and removes the injection path.
A CSS injection flaw in MISP's remote event preview page lets an operator of a linked MISP server write arbitrary CSS declarations into the local UI by embedding a payload in a remote tag's colour value; the injected style is rendered when a local user opens the preview for that remote event, enabling visual spoofing, UI manipulation, and narrow information disclosure but not script execution. Only instances below 2.5.48 are affected, and exploitation requires a pre-existing linked-server trust relationship, tag-creation privileges on the attacker-controlled server (authenticated, low-privileged per the CVSS vector), and deliberate victim interaction with the preview page. The vendor has released a patch (MISP 2.5.48, commit 91323b517) that validates tag colours against a strict hex pattern, and no public exploit code has been identified at time of analysis.
Information disclosure in IBM Concert 1.0 through 3.0.0 can expose sensitive heap-resident data to an authenticated local attacker with low privileges who is able to inspect the application's process memory, with high attack complexity and no public exploit identified at time of analysis. The flaw is CWE-244 (failure to clear heap memory before release), rated CVSS 4.7, and a vendor patch is available. Realistic risk is limited to post-compromise or insider scenarios on hosts where an attacker already has local access.
Missing authorization in openGauss Server 3.0.0 through 6.0.0 lets any authenticated low-privilege database user read raw table-data blocks without holding SELECT on the target table. The user can call pg_relation_filepath() to obtain the relation file path, including compressed _compress paths, then call pg_read_binary_file_blocks() to read blocks because the underlying ReadBinaryFileBlocksFirstCall() and is_row_data_file() checks cover path normalization and data-directory boundaries but not caller privileges. The issue is fixed in 7.0.0-LTS, has a CVSS score of 4.3 (PR:L, C:L), and no public exploit was identified at time of analysis.
Stored cross-site scripting in the WSO2 Carbon management console lets a high-privileged authenticated console user plant malicious JavaScript in event publisher or receiver property values, which executes when another console user opens the affected details page. The flaw requires adjacent-network access, high privileges, and victim interaction and is rated CVSS 4.3, with session hijacking prevented by httpOnly cookies. No public exploit identified at time of analysis and a vendor patch is available; the combined constraints make this a low real-world priority.
Authenticated IBM MQ users holding valid queue-manager credentials can trigger an off-by-one buffer overflow by submitting a specially crafted object name, causing process instability or a crash of MQ components. The impact is availability-only (CVSS 4.3, PR:L, A:L) with no path to data disclosure or code execution, and the CPE data confines affected deployments to containerized environments - IBM MQ Operator and IBM MQ Advanced Container Images - rather than traditional MQ installations. No public exploit code or confirmed active exploitation was identified at time of analysis, and the mandatory authentication step sharply limits exposure to insiders or attackers who have already obtained MQ credentials.
Improper input validation in the Rack Management Controller (RMC) on HPE Compute Scale-up Server 3200/3250 platforms and Superdome Flex servers allows a network-reachable, authenticated low-privilege user to list and modify files on the RMC filesystem (CVSS 3.1: 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). Impact is confined to the management-controller layer - exposure of RMC file contents plus limited integrity damage - rather than code execution or loss of availability on the managed compute partitions. No public exploit code was identified at time of analysis, and practical risk is further reduced because these RMC interfaces are normally deployed on segregated administrative networks.
Malformed compressed message data delivered to containerized IBM MQ deployments (MQ Operator and MQ Advanced Container Images) can drive a minor out-of-bounds read (CWE-125) in the decompression code path, but the broker rejects the malformed request and does not return the over-read bytes, so no message or memory contents are exposed. The attacker must already hold valid MQ connection credentials (CVSS PR:L) and clear high attack complexity (AC:H) by crafting a specific malformed compressed structure, keeping the issue at CVSS 3.1 (Low). No public exploit code or active exploitation has been identified at time of analysis, and IBM has published a vendor fix via its support portal.
Memory and task exhaustion in the russh SSH agent server (versions through 0.64.0) lets an unauthenticated attacker deny SSH agent service by sending a constrained add-key request packed with SSH_AGENT_CONSTRAIN_LIFETIME records. Each 5-byte lifetime record causes the agent to spawn a long-lived tokio task that clones the key blob, producing roughly 141x amplification; the public proof-of-concept in the advisory turned 10.2 MiB of protocol traffic into about 2.1 million live tasks and roughly 1.4 GB of RSS growth. Attackers can reach the agent socket locally or through agent forwarding to an attacker-controlled SSH server, and publicly available exploit code exists, though this is availability-only with no code execution or data disclosure.
Classified Listing, a WordPress classifieds plugin, through version 6.1.5 does not properly validate a specified quantity in input, allowing low-privileged authenticated users to reach functionality that ACLs should restrict and to read limited information (CVSS 4.3, confidentiality-only impact). The flaw is remotely reachable without user interaction but requires a logged-in account, such as one created through open registration commonly enabled on classifieds sites. No public exploit code or CISA KEV entry was identified at time of analysis.
Authorization bypass in the WordPress Event Tickets plugin (all versions through 5.30.1) lets an authenticated user tamper with user-controlled object keys and reach ticketing records that should belong to another attendee, customer, or event. Because exploitation requires a valid logged-in account (CVSS PR:L), the realistic exposure is limited to sites that permit self-registration or that automatically issue accounts to attendees and customers; the impact stays within unauthorized read/modification of ticketing objects (I:L, no confidentiality or availability effect), giving a moderate vendor score of 4.3. No public exploit code has been identified at time of analysis and the issue has not been added to CISA KEV.
Missing authorization in the FluentCommunity WordPress plugin (all versions through 2.11.0) lets an authenticated low-privileged member - for example a self-registered community user on a site with open registration - reach functionality that should be gated behind stricter access controls, resulting in limited information disclosure only (CVSS 4.3, C:L/I:N/A:N). The defect is a CWE-862 missing authorization check that is network-reachable, low-complexity and requires no user interaction, but its moderate rating reflects the prerequisite of an existing account. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Apache Camel's Jetty HTTP component (camel-jetty / camel-jetty-common), in versions 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0, installs Jetty's CrossOriginFilter with its stock defaults whenever an operator opts in with enableCORS=true, producing an allow-any-origin policy that also grants credentials instead of the empty policy operators expected to fill in. Unauthenticated remote attackers who lure a victim's browser to an attacker-controlled page (UI:R) can then perform credentialed cross-origin reads against the endpoint and read the responses, provided the victim already holds cookies or session credentials for that endpoint and the endpoint returns sensitive data. Exposure is configuration-dependent because it requires the non-default enableCORS=true opt-in on a Jetty endpoint; no public exploit code or active exploitation has been identified at time of analysis, and fixed versions 4.23.0, 4.18.5 and 4.22.1 have been released by the vendor.
Login CSRF in @fastify/oauth2 7.2.0 through 8.3.1 allows an attacker who has learned a valid OAuth2 state value to complete an authorization flow in a victim's browser and silently sign the victim in to the attacker's account, because state and code-verifier cookies set at login routes with two or more path segments lack a Path attribute and are not cleared by the callback's root-path deletion. The flaw is limited to multi-segment login routes and requires user interaction plus a known state value, is rated CVSS 4.2 with high attack complexity, and is fixed in 8.3.2; no public exploit code or CISA KEV entry was identified at time of analysis.
IBM Concert versions 1.0 through 3.0.0 persist web page content to a local on-disk cache that is not adequately protected, so a second user with an account on the same host can read cached page data belonging to another Concert user. The issue is strictly local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base score 4.0) and impacts confidentiality only - there is no network attack path, no integrity or availability effect, and single-user or isolated deployments where no other principal can reach the cache are not meaningfully exposed. Exploitation requires an attacker to already hold local/interactive access to the host; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. A vendor patch is available.
Login cross-site request forgery in the SAML authentication flow of the AWS auth manager shipped in apache-airflow-providers-amazon allows a remote attacker to silently log a victim into the attacker's own Airflow account, so that any work the victim subsequently performs lands in a session the attacker controls. Deployments of the Amazon provider before 9.38.0 that use the AWS auth manager configured with SAML authentication are affected; the attacker needs no Airflow account or credential but must induce the victim to load an attacker-controlled page, so user interaction is required and impact is limited to partial confidentiality and integrity with no availability effect. No CISA KEV entry, public exploit code, or EPSS score was supplied at time of analysis, so there is no public exploit identified at time of analysis, and the defect is the same login-CSRF class already fixed in the Keycloak auth manager as CVE-2026-40948.