Vulnerabilities

Cisco Identity Services Engine (ISE) and the Cisco ISE Passive Identity Connector (ISE-PIC) contain an incorrect use of privileged APIs flaw (CWE-648) affecting the web-based management interface. An unauthenticated, remote attacker with network access to that interface can send requests that invoke privileged APIs without authenticating, bypassing the interface's access controls. Successful exploitation grants the attacker unauthorized access to the affected device, presumably with the administrative capabilities available through the management interface, such as control over network access policy and visibility into identity data. Any organization running an affected Cisco ISE or ISE-PIC release is potentially affected, with risk highest where the management interface is reachable from untrusted networks. The flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2026-09-16, indicating exploitation in the wild, though no public proof-of-concept is known and CVSS scoring is pending.

Do: Upgrade ISE and ISE-PIC to the fixed releases specified in Cisco's security advisory (fixed versions are not provided in the available data); because the flaw is on CISA's KEV list, federal agencies must patch or apply mitigations per BOD 26-04 timelines. Until patched, restrict access to the web-based management interface to trusted administrative networks only, verify no unintended exposure via firewalls/ACLs, and monitor for unauthenticated access attempts against the interface.

A logic error in the cellular modem component causes an improper authorization check (CWE-285/CWE-693), allowing a permission bypass. An attacker who already has low privileges and is on an adjacent network (proximal, e.g., a hostile local or cellular-adjacent network) can trigger the flaw without any user interaction, and successful exploitation yields remote escalation of privilege with high impact on confidentiality, integrity, and availability (CVSS 3.1 base score 8.0). The flaw was assigned through Google's device security CNA ([email protected]), consistent with modem firmware shipped in Google Pixel-class devices; specific affected firmware versions were not provided in the source data. No public proof-of-concept is known, the issue is not listed in CISA's KEV catalog, and there is no evidence of exploitation in the wild. Defenders should treat this as a patch-on-next-bulletin item unless devices operate in high-risk adjacent-network environments.

Do: Install the latest Google monthly security update that includes the cellular modem firmware patch and verify the device's security patch level reflects it. Because exploitation requires network adjacency plus some existing privilege, prioritize devices used in high-risk or shared-network settings and watch for indicators of rogue femtocell/base-station or hostile local-network activity. With no public PoC or KEV listing, standard monthly patch cadence is reasonable outside those high-risk scenarios.

Concrete CMS versions before 9.5.3 fail to escape or integer-cast the stored width and height values of the YouTube block, applying only a trim() before printing them into iframe HTML attributes, which allows stored cross-site scripting. A user with edit_block permission on the YouTube block can inject an event handler (e.g., in the width/height attribute values) that executes attacker-controlled JavaScript in the browser of any visitor rendering the page. If the victim is an administrator, the injected script runs with administrative privileges, enabling actions such as creating new admin accounts or modifying site content and settings. Affected installations are those running Concrete CMS before 9.5.3 where users with edit_block permission are not fully trusted. No public proof of concept is known, the flaw is not in CISA's KEV catalog, and there is no evidence of in-the-wild exploitation at this time.

Do: Upgrade to Concrete CMS 9.5.3 or later, which escapes/casts the YouTube block's width and height values. Review existing YouTube blocks for unexpected HTML event-handler content in the width and height fields and check block version history for suspicious edits by low-privileged users. Restrict edit_block permissions on pages to trusted staff, since the flaw requires an account with editing rights to exploit, and consider rotating admin sessions if a compromised editor is identified.

Cisco AsyncOS Software for Cisco Secure Email Gateway contains a SQL injection flaw (CWE-89) in its email parsing logic, caused by insufficient validation of message content. An unauthenticated, remote attacker can trigger it simply by sending a crafted email containing malicious SQL statements through an affected gateway, with no user interaction required. Successful exploitation allows arbitrary SQL execution that escalates to arbitrary operating-system command execution with root privileges, fully compromising the appliance and all mail flowing through it. Any organization running an affected version of Cisco Secure Email Gateway is impacted, and because these appliances sit on the inbound mail path they are inherently reachable over the network. There is no known public proof-of-concept, the flaw is not on the CISA KEV list, and no in-the-wild exploitation has been reported to date, though the CVSS 9.8 rating makes patching urgent.

Do: Upgrade to the fixed AsyncOS release listed in the corresponding Cisco PSIRT advisory as soon as possible, since the flaw is unauthenticated, requires no user interaction, and yields root. Until patched, apply any Cisco-documented workarounds and tightly restrict which hosts can submit mail to the gateway where operationally feasible. Review mail and system logs on these appliances for anomalies such as SQL errors in parsing, unexpected processes, or unexplained outbound connections that could indicate exploitation attempts.

strongSwan's libcharon, the component implementing IKEv2/IPsec key negotiation in the charon daemon, contains a use-after-free (CWE-416) in its handling of IKEv2 rekeying collisions, affecting versions 6.0.0 through 6.0.7. The flaw is triggered when two peers simultaneously initiate rekeying of the same security association and the daemon frees an object that the colliding rekey transaction still references; because the CVSS vector scores network attack complexity as high with low privileges required, an attacker needs to be a valid (authenticated) IKEv2 peer and hit a timing-dependent race condition. Successful exploitation can crash the VPN daemon, and the high confidentiality/integrity/availability impacts in the score indicate memory corruption that could potentially extend to code execution in the context of the daemon. Anyone running strongSwan 6.0.0 through 6.0.7 as an IKEv2 responder or initiator — including VPN gateways, site-to-site tunnel endpoints, and appliances or distributions that bundle the 6.0.x series — is affected. No public proof-of-concept, in-the-wild exploitation, or CISA KEV listing is known at the time of this analysis.

Do: Upgrade strongSwan to a release newer than 6.0.7 once the fix is published — check the upstream release notes or security advisories for the patched 6.0.x version, as the affected range ends at 6.0.7. Until then, restrict IKEv2 access (UDP 500/4500) to trusted, authenticated peers via firewall rules or peer allowlists, and monitor VPN gateways for unexpected charon daemon crashes or restarts. Because exploitation requires valid IKEv2 credentials and a hard-to-hit race condition (AC:H), exposure to unauthenticated attackers is limited, but authenticated VPN peers should be treated as potential sources of malicious rekey traffic.

IBM Langflow OSS versions 1.0.0 through 1.11.5 contain a code injection flaw (CWE-94) that occurs during graph construction, the process by which Langflow builds executable AI/agent workflow graphs. Because the CVSS 3.1 vector is network-exploitable with low complexity, no privileges, and no user interaction, a remote attacker who can reach the service can inject and execute arbitrary code on the underlying server without authenticating. Successful exploitation gives full control of the host — confidentiality, integrity, and availability are all rated high impact — and typically exposes any API keys, model credentials, or data configured in Langflow flows. All organizations running self-hosted IBM Langflow OSS in the affected range are at risk, especially instances exposed to the internet. As of now there is no known public proof of concept, no confirmed in-the-wild exploitation, and the flaw is not on the CISA KEV list, though the severity makes pre-patching attention warranted.

Do: Upgrade IBM Langflow OSS to a release newer than 1.11.5 as soon as a fixed version is available from IBM. If patching must wait, remove the instance from internet exposure (place behind a VPN or authenticated reverse proxy) since exploitation requires no credentials or user interaction. Review logs for unauthenticated requests to graph-construction/flow endpoints and for unexpected Python process or outbound network activity originating from the Langflow server.

Suricata, the open-source network Intrusion Detection/Prevention and Network Security Monitoring engine, contains a type confusion flaw (CWE-843) in its HTTP/2 handling that occurs when a protocol change is processed during traffic inspection. An attacker who can send crafted HTTP/2 traffic across a link monitored by Suricata can trigger the flaw without authentication or user interaction, crashing the engine and causing denial of service. The CVSS 9.1 (critical) rating reflects high integrity and availability impact with no confidentiality loss, and the crash risk is especially serious for inline IPS deployments where sensor failure disrupts inspection. All Suricata versions prior to 7.0.16 (7.0.x branch) and prior to 8.0.5 (8.0.x branch) are affected. No public proof-of-concept or in-the-wild exploitation is currently known, and the issue is not in CISA's KEV catalog.

Do: Upgrade Suricata to 7.0.16 (7.0.x branch) or 8.0.5 (8.0.x branch), including patched builds supplied by appliance or distribution vendors that bundle the engine. If upgrading is not immediately possible, disable HTTP/2 parsing where it is not required, as this is the documented workaround. Prioritize inline IPS deployments, where a crash from crafted HTTP/2 traffic has the greatest operational impact.

CVE-2026-88032 is a use-after-free (CWE-416) in the reactive client-side encryption component of the MongoDB Java Driver, in which native resources can be freed while a still-running encrypted operation is using them. The issue is reachable only when the application uses a reactive encryption configuration that retrieves KMS credentials on demand, and it is triggered when an attacker or component able to cause such an in-flight encrypted operation to be cancelled does so. The result is an availability-only impact: the hosting application process can terminate, with no confidentiality or integrity loss (CVSS 4.0 vector shows VA:H with VC:N/VI:N, scored 8.2 High). Affected parties are JVM application developers embedding the MongoDB Java Driver with reactive streams plus client-side encryption and on-demand KMS credential retrieval; MongoDB deployments that do not use client-side encryption, or that use the sync/standard async drivers, are not affected. No public proof-of-concept is known, the issue is not in CISA's KEV catalog, and no in-the-wild exploitation has been reported.

Do: Audit JVM applications for use of the MongoDB Java Driver's reactive streams API with client-side encryption configured to fetch KMS credentials on demand; if present, upgrade to the fixed driver version identified in MongoDB's security advisory (version numbers not provided in the available data). Until patched, limit which callers can cancel in-flight encrypted operations, and monitor MongoDB's advisory for version and mitigation details.

Tesseract OCR 5.5.3 and earlier fails to validate counts read from the legacy INTTEMP component of .traineddata files: Classify::ReadIntTemplates uses NumClassPruners, NumClasses, and NumProtoSets as loop bounds without capping them against their maximums, and writes heap pointers past the fixed-capacity ClassPruners and ProtoSets arrays. An attacker who can supply or replace a .traineddata file consumed by Tesseract triggers this during legacy-classifier initialization, before any OCR output, gaining heap corruption, a crash (denial of service), or potentially controlled corruption. All deployments running Tesseract 5.5.3 or earlier are affected, particularly applications, document pipelines, and services that load traineddata files from untrusted or user-controlled sources. No fixed release is available as of this review, and no public proof-of-concept, KEV listing, or known in-the-wild exploitation exists.

Do: No patched version is available yet, so mitigate by ensuring Tesseract only loads .traineddata files from trusted sources and treat user-supplied traineddata as untrusted input. Deployments using only LSTM-based recognition can check whether their pipelines load legacy INTTEMP components, since the flaw is reached during legacy-classifier initialization. Monitor the tesseract-ocr GitHub repository for a fixed release and upgrade promptly once published.

Flowise 3.1.2 contains an improper code generation control flaw (CWE-94, code injection) in its /api/v1/prediction/ API endpoint. A remote, unauthenticated attacker can send a crafted request to this endpoint to execute arbitrary code on the server hosting Flowise, achieving full confidentiality, integrity, and availability impact (CVSS 9.8) under the application's privileges. Only version 3.1.2 is named in the available data; the full range of affected versions and any patched release are not specified. As of the provided data, the issue is not listed in CISA's KEV and no public proof-of-concept or confirmed in-the-wild exploitation is known. The critical rating reflects that the flaw is network-reachable with no privileges or user interaction required.

Do: Inventory Flowise deployments and identify any running version 3.1.2; upgrade to a patched release as soon as the vendor publishes one (no fixed version is named in the current data), and monitor the Flowise GitHub repository for an official advisory. Until patched, restrict access to /api/v1/prediction/ by enforcing authentication, binding the service to internal interfaces, or adding reverse-proxy/firewall rules. Review logs for unexpected or unauthenticated requests to that endpoint as a sign of probing or exploitation.

rclone's `serve s3` command, when configured with an --auth-proxy but without --auth-key, registers any client-chosen access key ID with an empty secret and passes that identifier to the proxy without an independent per-identity credential. An unauthenticated network attacker can send an S3 request signed via SigV4 with an arbitrary access key ID and an empty secret; because both authPairMiddleware and gofakes3 validate against that same empty secret, the signature verifies and the request is accepted. The attacker then reaches whatever backend the auth-proxy script resolves for the chosen identity, with high impact on confidentiality, integrity and availability (CVSS 9.8). Only deployments running rclone prior to 1.75.1 with `serve s3`, --auth-proxy enabled and no --auth-key are affected; other rclone configurations are not implicated. No public proof-of-concept is known and the issue is not in the CISA KEV catalog, so no confirmed exploitation has been reported.

Do: Upgrade to rclone 1.75.1 or later. If upgrading is not immediately possible, set --auth-key on `serve s3` deployments that use --auth-proxy, or restrict network access to the S3 endpoint to trusted clients. Check serve s3 access logs for successful requests using unexpected or arbitrary access key IDs, which would indicate exploitation attempts.

CVE-2026-84869 is a critical authorization flaw (CWE-862 missing authorization, CWE-269 improper privilege management) in the ScreenConnect client, the endpoint-side agent of ConnectWise's widely used remote access and remote support platform, in which files can be transferred to a machine and executed during an active remote session without the expected authorization or without confirmation by the Host (technician). It is triggered in certain circumstances during an active session, with a network attack vector, low attack complexity, low privileges required, and no user interaction per the CVSS 3.1 vector. An actor who obtains or already holds access to a session context could thereby push and run files on the managed endpoint, potentially achieving code execution with high confidentiality, integrity, and availability impact (CVSS 3.1 score 9.9, scope changed). Only endpoints running the ScreenConnect client are affected; ScreenConnect servers are not impacted, and the affected client version ranges are governed by ConnectWise security advisory AV26-903 (not enumerated in the available data). The flaw is not currently known to be exploited: it is not in CISA KEV, no public proof of concept is known, and EPSS assigns a modest 0.4% probability of exploitation within the next 30 days (32nd percentile).

Do: Follow ConnectWise security advisory AV26-903 and update ScreenConnect clients to the patched version it specifies, noting that ScreenConnect servers do not require remediation. Until patching is complete, monitor active remote sessions, require Host confirmation for file transfers, and review recent sessions on high-value endpoints for unexpected transferred or executed files; given no known exploitation and the active-session prerequisite, prioritize endpoints routinely accessed remotely.

JFrog Artifactory contains an improper authentication flaw (CWE-287) in which the server may return its internal anonymous-user token to an unauthenticated caller, even on instances where anonymous access is disabled. An attacker triggers the issue by sending unauthenticated requests to the affected Artifactory interface over the network; the vector requires no privileges or user interaction and is of low complexity. Successful abuse yields the internal anonymous-user token, which can then be used to reach sensitive resources (such as repositories or artifacts) that should be protected when anonymous access is disabled, with high confidentiality impact but no integrity or availability impact. Any organization running an affected JFrog Artifactory deployment - particularly those relying on disabled anonymous access as a control - is affected, though only instances where the vulnerable endpoint is reachable are actually exposed. Exploitation has been reported in the wild as part of an ongoing Artifactory attack campaign alongside CVE-2026-42016 and CVE-2026-82329, although there is no public PoC and the flaw is not yet in the CISA KEV catalog.

Do: Upgrade Artifactory to the fixed release identified in JFrog's security advisory (JFrog is the assigning CNA; exact version numbers are not included in the available data). Until patched, restrict unauthenticated network access to Artifactory, verify the anonymous-access configuration, and review logs for unauthenticated requests that retrieved tokens or accessed sensitive resources. Because in-the-wild exploitation has been reported alongside CVE-2026-42016 and CVE-2026-82329, patch for all three and consider rotating internal/anonymous tokens and auditing artifact access.

JFrog Artifactory (Self-Hosted) versions before 7.133.11 fail to validate a token's scope, checking only the token's signature and issuer, which constitutes an incorrect authorization flaw (CWE-863). A remote, authenticated user with low privileges can obtain or present a token whose scope is never verified, bypassing authorization checks and escalating to higher privileges. Successful attackers gain administrative control of the Artifactory instance; in observed attacks this flaw has been chained with CVE-2026-42018 and CVE-2026-82329 to bypass authentication, take admin control, and deploy backdoor malware. Only self-hosted Artifactory deployments are within the stated affected scope. Exploitation is confirmed in the wild and the vulnerability was added to CISA's KEV catalog on 2026-09-11, although no public proof-of-concept code is known.

Do: Upgrade self-hosted Artifactory to version 7.133.11 or later immediately, in line with vendor instructions and CISA KEV/BOD 26-04 timelines. Audit issued tokens and logs for tokens carrying elevated scope granted to low-privilege users, and look for signs of compromise such as unexpected admin accounts or persistence, given reported backdoor deployments. Also patch CVE-2026-42018 and CVE-2026-82329, which attackers are chaining with this flaw.