Unauthenticated access control bypass in Cisco Secure Firewall ASA and Cisco Secure Firewall Threat Defense (FTD) software lets a remote attacker send traffic that the device's access control list is supposed to block, potentially reaching hosts on protected networks. Exploitation is conditional: the device must have an ACL configured with Object Group Search (OGS) enabled and object groups populated into group access control policies, a logic error in that population step causes the wrong policy to be applied. The issue is rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), while no public exploit identified at time of analysis, and it is not confirmed actively exploited (CISA KEV) - the practical risk is moderate and configuration-dependent rather than a critical emergency.
Missing authentication on a function of the Online Certificate Status Protocol (OCSP) responder in Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) lets an unauthenticated, remote attacker trigger an on-demand reload of the responder's certificate and key material. Affected deployments span essentially the current ISE 3.1 through 3.5 release trains and the corresponding ISE-PIC builds, with any host reachable to the OCSP responder service in scope. The impact is limited to a low-severity availability disruption (CVSS 3.1 base 5.3, A:L) with no confidentiality, integrity, or host-compromise consequence; no public exploit code or confirmed active exploitation was identified at time of analysis, and external risk scoring (EPSS) was not available in the supplied data.
Missing authentication on the internal Policy Runtime Repository Table (PRRT) service in Cisco Identity Services Engine (ISE) and the Cisco ISE Passive Identity Connector (ISE-PIC) allows an unauthenticated, remote attacker to retrieve sensitive configuration information from an affected device. The flaw is an instance of CWE-306 (missing authentication for a critical function) and carries a CVSS 3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), reflecting confidentiality-only impact with no modification or denial-of-service effect. Affected releases span ISE 3.4.0 through 3.4 Patch 6, ISE 3.5.0 through 3.5 Patch 3, and ISE-PIC 3.4.0/3.5.0; there is no public exploit identified at time of analysis. Real-world risk is tempered by the fact that the vulnerable PRRT service is internal, so exploitation depends entirely on an attacker gaining network reachability to that endpoint - segmentation of ISE management and internal interfaces sharply reduces exposure.
Unauthenticated path traversal in the Cisco ISE and ISE-PIC client provisioning download service allows a remote attacker to read protected files on the appliance by sending a crafted provisioning resource request containing directory traversal sequences. The flaw affects Cisco Identity Services Engine software across the 3.1 through 3.5 release families (and the corresponding ISE Passive Identity Connector 3.1.0, 3.2.0, 3.3.0, 3.4.0 and 3.5.0 builds) and needs only network reachability to the provisioning/onboarding endpoint, with no credentials or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation, but the low attack complexity and unauthenticated reach make prompt patching advisable, especially where the ISE guest/BYOD portal is published beyond the internal onboarding network. Overall this is a genuine but modest-severity issue whose impact is limited to information disclosure.
Unauthenticated remote attackers who can reach the Cisco Identity Services Engine guest portal can submit forged endpoint posture status events into ISE's posture pipeline, allowing manipulation of the posture state recorded for endpoints. The issue is an authentication gap (CWE-306) on an internal posture-status reporting interface that the guest portal exposes; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no credentials, privileges, or user interaction are required, and the assessed impact is integrity-only and low (C:N/I:L/A:N). Affected deployments span Cisco ISE Software 3.1 through 3.5 and the matching Cisco ISE Passive Identity Connector releases, and the practical exposure depends on whether the guest portal and posture assessment are enabled and reachable; no public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was provided.
Denial of service in Arista EOS affects devices that have VRRPv2 with IP Authentication Header (IP-AH) authentication explicitly configured - a non-default hardening option, so exposure is limited to networks that opted into it. An unauthenticated attacker positioned on the same layer-2 segment as the VRRP group can passively capture a legitimate authenticated VRRP advertisement and replay it indefinitely, keeping a stale master state alive and preventing a backup router from taking over the virtual gateway; hosts relying on that gateway address then lose connectivity. Impact is availability-only (no confidentiality or integrity loss, no code execution), the assessed severity is low (CVSS 3.1 5.3, AV:A/AC:L/PR:N/UI:N/A:L), and no public exploit code has been identified at time of analysis; exploitation requires layer-2 adjacency, which generally implies an insider, a compromised local host, or VLAN/physical access.
Server-side request forgery in LiteLLM Proxy versions prior to 1.83.9 lets an authenticated caller holding a valid virtual key redirect the gateway's outbound LLM traffic to an internal or external host of their choosing by placing api_base (or base_url) inside the user_config object of the request body instead of at the top level. Because is_request_body_safe in pre-1.83.9 only banned those keys at the top level and never inspected user_config, and because user_config feeds outbound router construction, the nested destination survives the safety check and reaches endpoints the caller could not otherwise access. The result is blind SSRF with low confidentiality impact against the proxy's network context rather than data theft or code execution; exploitation requires a working virtual key (PR:L, no user interaction), and no public exploit code has been identified at time of analysis.
Quadratic-complexity denial of service in the Svelte devalue JavaScript deserializer (all versions prior to 5.9.2) lets remote attackers stall Node/browser consuming processes by feeding a crafted serialized string to devalue.parse. Because the parser fails to reject indices greater than or equal to values.length in src/parse.js, a payload can alternate between array representations and force work that grows quadratically with payload size; the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) confirms this is unauthenticated and requires no user interaction, with impact limited to availability. Exploitation is deployment-conditional: the target application must actually call devalue.parse (or unflatten) on untrusted input - a library that only round-trips trusted internal data is not exposed regardless of version. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and EPSS data was not provided; the issue is fixed by rejecting out-of-bounds indices in version 5.9.2.
Malformed PFCP Session Report Request messages can abort the Open5GS SMF daemon, taking down all sessions handled by that SMF instance: in Open5GS through 2.8.0 the handler smf_n4_handle_session_report_request() signalled failure with a PFCP cause value that the caller in gsm-sm.c conflated with a session-release trigger, so a report with missing or inconsistent IEs drives execution into a reachable assertion (CWE-617) and terminates the process. The flaw is remotely triggerable by any host that can reach the SMF's N4/PFCP interface - normally the internal control-plane segment shared with the UPF - and because PFCP has no built-in authentication, no credentials are required once network reachability exists; the practical limiting factor is that N4 is not an internet-facing interface, not authentication. The authoritative assessment rates this AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (High availability impact only, no confidentiality or integrity impact), and no public exploit code has been identified at time of analysis, though an upstream fix commit is available.
Missing authorization in the ChangeWeDer CRM UserController index endpoint allows a remote attacker with a low-privilege authenticated account to reach functionality or data that should require stronger privileges, with limited confidentiality, integrity, and availability impact. The product has no versioning scheme and the project has not responded to the issue report, so no patched release is confirmed; exploitation requires network access to the Java CRM application and a valid low-privilege session. No public exploit identified at time of analysis.
Broken authorization in Concrete CMS 9 through 9.5.3 allows an authenticated user who already holds edit-board-contents permission on one board instance to query the custom-slot preview endpoint with an InstanceItem identifier belonging to a different board instance, causing the system to return summary fields - including the underlying page title and description - for pages that user is not permitted to view. The endpoint fails both to validate that the submitted item belongs to a board the requester is authorized to edit and to enforce page-view permission before generating the page-backed summary content. Rated CVSS v4.0 5.3 (our independent assessment: CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), this is a low-to-moderate severity IDOR-class information-disclosure flaw with no published exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV); no user interaction is required, but exploitation is gated behind an authenticated account with per-board edit permission.
Account lockout in the Red Hat build of Keycloak 26.4 and 26.6 lets an unauthenticated remote attacker deny access to a targeted user by registering that user's username on a trusted external identity provider, triggering a username collision during the first-broker-login flow. Exploitation requires the affected realm to be configured for identity brokering with an external IdP and to perform account linking by username, and the attacker must know or guess the victim's Keycloak username; no credentials or victim interaction are needed. Impact is limited to denial of access for one specific user (CVSS 5.3, AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:L, CWE-287), with no data exposure or account takeover, and no public exploit has been identified at time of analysis. Fixed versions are Red Hat build of Keycloak 26.4.16 and 26.6.7.
Server-side request forgery in Hippo4j through 1.5.0 allows an authenticated user of the Hippo4j server console to force the application to issue outbound HTTP GET requests to arbitrary hostnames and ports, because four ThreadPoolController endpoints accept a clientAddress parameter without validation. Affected deployments are those running the Hippo4j console with reachable internal services or cloud metadata endpoints (for example 169.254.169.254); the CVSS v3.1 score is 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), reflecting a confidentiality-only impact gated behind a valid console session (PR:L) with no user interaction. No public exploit code or confirmed active exploitation was identified at time of analysis, and the practical impact against cloud environments depends on whether the instance exposes a metadata service and on whether the affected endpoints return the fetched response body, which is not confirmed by the available source data.
Server-side request forgery in MLRun through 1.11.0 lets an authenticated user who can create or update a run attach a malicious WebhookNotification that makes the API server issue arbitrary outbound HTTP requests once that run transitions to a terminal state. Because the request originates from inside the cluster, it can be aimed at internal services, the in-cluster Kubernetes API, or cloud metadata endpoints such as 169.254.169.254, although the SSRF is blind/semi-blind and practical impact depends on egress filtering and metadata access in the target deployment. Rated 5.3 (CVSS:4.0) with low confidentiality and integrity impact and no availability impact; no public exploit identified at time of analysis.
Memory amplification in ISC BIND 9's negative cache allows remote, unauthenticated attackers to inflate resolver memory usage by supplying crafted authoritative responses. When a query response carries multiple copies of a record that should exist only once (for example an SOA record) with identical RDATA, named appends each copy to the in-memory RDATA set instead of discarding duplicates, so negative-cache entries retain more data than they should; BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, plus the corresponding -S1 subscription builds, are affected. The assessed impact is limited to gradual memory growth (availability low, no confidentiality or integrity effect, no crash demonstrated) and exploits require the attacker to be positioned to answer the resolver's upstream queries; no public exploit identified at time of analysis, and vendor fixes are available in 9.20.29 and 9.21.26.
Resource exhaustion in ISC BIND 9 recursive resolvers allows a remote, unauthenticated attacker to degrade name-resolution service by causing the resolver to process responses that contain large numbers of a specific class of invalid DNSSEC record, driving excessive CPU and memory consumption (CVSS 3.1 base 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L). Affected builds are 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, plus subscription (-S1) equivalents 9.11.3-S1 through 9.18.50-S1 and 9.20.9-S1 through 9.20.27-S1; authoritative-only deployments are not the described target. The impact is capped at availability degradation rather than a full outage because BIND's default limits on 'max-records-per-type' and 'max-types-per-name' already throttle the offending inputs, and operators who have raised or disabled those limits carry materially higher exposure. There is no confirmed active exploitation (no CISA KEV listing) and no public exploit identified at time of analysis; vendor-released patches are available as 9.20.29 and 9.21.26.
OpenFGA releases prior to 1.18.1 can have their ListUsers API return a user who should have been excluded by the authorization model, causing applications that use ListUsers to enumerate or enforce access to treat an excluded subject as authorized. The flaw is triggered only by a specific combination: a relation expressed as an intersection containing an exclusion operand (for example 'viewer: (org_member but not banned) and active'), where the included base is granted through a type-bound public wildcard ('user:*') and the excluded user also holds a concrete tuple satisfying another intersection operand. It is remotely reachable (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N, base 5.3) but limited to callers already authorized to invoke ListUsers, and it does not affect the Check API in the vendor's reproducing tests; no public exploit code or CISA KEV listing was identified at time of analysis, and the issue is fixed in 1.18.1.
Broken access control in the Adenion Blog2Social plugin for WordPress before 9.1.0 lets any authenticated user holding the edit_posts capability (Contributor role or higher) reschedule, suppress, or otherwise alter the scheduled social-media post records belonging to other users. The issue is remotely reachable over HTTP with no user interaction, but exploitation is gated by low-privilege authentication and by the presence of other users' scheduled posts, so cross-user impact is negligible on single-author sites. It is rated CVSS 4.0 5.3 (Medium); there is no public exploit identified at time of analysis and no CISA KEV listing, and a vendor patch is available.
User email disclosure in Adenion's Blog2Social WordPress plugin before 9.1.0 allows any authenticated user holding the edit_posts capability to enumerate and retrieve the email addresses of every registered account on the site, including administrators. The b2s_search_user AJAX handler fails to restrict callers to those with the list_users capability, turning a routine user-search function into a bulk contact-harvesting primitive for low-privileged insider or subscriber-level accounts. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; the practical risk is data-harvesting and follow-on phishing rather than code execution, so this is a genuine but modest-severity information-disclosure issue rather than a high-impact priority.
Inefficient algorithmic complexity (CWE-407) in vLLM up to and including 0.29.0 causes the thinking-budget marker search in vllm/v1/sample/thinking_budget_state.py to re-scan an ever-growing output token buffer on every decode step, degrading throughput and consuming CPU when serving reasoning-capable models. An authenticated API client (CVSS 4.0 vector lists PR:L) that sets the thinking_token_budget sampling parameter can trigger the quadratic blowup, but only when the generated output never contains the configured reasoning start/end marker token sequences, so the internal search cursors fail to advance; the practical worst case is partial availability loss (slowed or stalled generation per affected request) rather than a crash, code execution, or any confidentiality/integrity impact. This is a low-severity availability issue - no public exploit code has been identified at time of analysis and there is no CISA KEV listing - and the vendor score of 5.3 is well calibrated to the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L. Upstream fix is available as GitHub PR vllm-project/vllm#51133, which awaits acceptance, so no released patched version is independently confirmed.
User account enumeration in the Adenion Blog2Social plugin for WordPress before 9.1.0 lets any authenticated user holding the edit_posts capability - such as a Contributor, Author, Editor, or Administrator - resolve arbitrary numeric user IDs to their display names and confirm whether those accounts exist. The bug is an authorization bypass through a user-controlled key (CWE-639) in the b2s_get_select_mandant_user AJAX handler, which returns user data for the attacker-supplied owner parameter without checking that the caller is allowed to read account information; the CVSS 4.0 base score is 5.3 (Medium) and the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, meaning confidentiality-only impact with no modification or availability effect. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation; practical risk is concentrated on sites that allow open or self-registration or that host many low-trust contributor accounts, since a valid low-privileged login is a strict prerequisite.
Unauthenticated attackers within Bluetooth range can modify brain stimulation parameters on Sooma 2GEN tDCS home therapy devices, potentially disrupting therapy or causing unintended stimulation. The flaw (CWE-924) stems from missing integrity and authentication checks on Bluetooth control messages; exploitation requires only physical proximity, with no privileges or user interaction needed. No public exploit code or active exploitation has been identified at time of analysis, and no vendor-released patch is identified at time of analysis.
Unbounded memory growth in the ag-ui (AG-UI protocol) C++ community SDK's Server-Sent Events parser lets an attacker who can control or influence the consumed SSE stream exhaust the parsing process's memory, producing a denial of service. The flaw lives in sdks/community/c++/src/stream/sse_parser.cpp, where the buffer guard compares only m_buffer plus the incoming chunk against kMaxBufferSize and ignores the per-event accumulator m_currentData, so a single event that is never terminated by a blank line and delivered as many small chunks grows without bound. It is rated CVSS 5.3 (CVSS:4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L) / CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, availability-only and requiring the low-privilege, authorized position of the stream producer; no public exploit identified at time of analysis, and an upstream fix is available (commit ab6e0bc, PR #2501).
Memory exhaustion in the AG-UI Go community SDK's SSE client allows a remote attacker who controls or can intercept an SSE endpoint to drive the client process out of memory by sending a stream that never terminates a line, or an oversized single frame. The affected component is sdks/community/go/pkg/client/sse/client.go in ag-ui, and impact is availability-only with no data disclosure or modification, consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L. No public exploit was identified at time of analysis; an upstream fix exists as pull request #2700 but a released patched version is not independently confirmed.
Origin validation errors in the AG-UI TypeScript client SDK (ag-ui 1.0) allow remote, low-privileged attackers who can influence an agent event stream to bypass event-origin checks and release the pending-interrupt gate, yielding low confidentiality, integrity, and availability impact. Affected deployments are those consuming untrusted or compromised AG-UI event sources; the advisory describes manipulation of the TEXT_MESSAGE_START argument, while the upstream fix PR #2701 also addresses an interrupt/resume state flaw where a stream emits an interrupt outcome and then finishes a subsequent run without a resume. Independent assessment rates this medium severity (vendor CVSS 4.0 base 5.3) with no signals of elevated real-world risk; no public exploit identified at time of analysis, and no CISA KEV entry.
Information disclosure in the a2ui agent-to-UI rendering library (versions 0.8, 0.9, and 1.0) lets a caller that can drive an A2UI surface read JavaScript prototype-chain members - such as __proto__, constructor, toString, and valueOf - through the Model Processor's data-binding path resolver, leaking internal object structure rather than application data. The flaw is an unauthenticated-of-the-network-but-role-limited (CVSS PR:L) defect in model-processor.ts, where path segments are evaluated as current[segment] without an own-property check; impact is limited to low confidentiality loss with no integrity or availability effect, and there is no public exploit identified at time of analysis. Vendor risk is low-to-moderate: a fix exists upstream as commit 1b3bff23 (PR #2355), but no tagged patched release has been independently confirmed.
Resource exhaustion in the a2ui component framework versions 0.9 and 0.9.1 allows remote attackers with low-privilege authenticated access to degrade availability by invoking the updateComponents function of basic_functions.ts with manipulated input. Impact is confined to a low availability effect (VA:L) with no confidentiality or integrity loss, and the vendor was notified through a public issue report but has not responded or produced a fix. No public exploit code and no confirmed active exploitation were identified at time of analysis, and because a2ui is a niche, early-version open-source project with minimal deployment, the practical risk is low to moderate despite the CVSS 4.0 base score of 5.3.
Cross-site scripting in the a2a-chat-canvas markdown rendering component of a2ui (a2ui-project) up to version 0.10.7 allows a low-privileged authenticated user to plant script that executes in another user's browser when the chat canvas renders the crafted content. The defect lives in samples/community/client/angular/projects/a2a-chat-canvas/src/lib/services/sanitizer-markdown-renderer-service.ts, where markdown is converted to HTML without fully neutralizing dangerous markup, yielding an integrity/behavior impact (VI:L) rather than data disclosure (VC:N). There is confirmed CISA KEV status: no active exploitation has been reported, no public exploit code exists, and tracking is currently handled through a public GitHub issue rather than a formal vendor security bulletin.
Arista EOS devices that run OpenConfig-based management services (gNMI, gNSI, RESTCONF, NETCONF) can inadvertently write sensitive request and response payloads into logs that persist on the local switch or are forwarded to remote accounting/AAA servers. The leaked material includes plaintext CLI secrets such as 'username bob secret myPass' and sensitive OpenConfig YANG leafs like system/aaa/global/tacacs/config/secret-key, so the exposure is a credential/secret disclosure problem rather than an integrity or availability issue. Exploitation requires that those services be enabled, that secrets actually transit them, and that an attacker obtain read access to the resulting log or accounting sinks; triggering also requires an authenticated actor (PR:L) and some user interaction (UI:P) per the assessed vector. The issue was found internally by Arista, which states it has no evidence of malicious exploitation in customer networks, and no public exploit code has been identified at time of analysis. gRPC-based streaming telemetry from the Streaming Telemetry Agent to CloudVision is explicitly not affected.
CSS injection in the A2UI Angular Renderer (a2ui-project/a2ui through 0.10.6) lets a party who controls server-to-client messages embed arbitrary strings in the theme.primaryColor field, which the renderer writes unvalidated into the host element's --a2ui-color-primary CSS custom property. Because the theme is declared with z.any() in renderers/web_core/src/v0_9/schema/server-to-client.ts, values such as url(https://attacker.example/beacon) bypass validation and reach the DOM style layer, enabling UI spoofing, outbound request beacons and potential data exfiltration from affected Angular applications. Exploitation requires the ability to inject or manipulate the message stream consumed by the renderer (PR:L) plus a passive user action (UI:P); the vendor has published fix commit fb8e85aec78d04e81feb9992a57638ca1ec4dc1b (PR #2367). There is no CISA KEV listing and no public exploit identified at time of analysis.
Stored cross-site scripting in Craft CMS (5.7.0 through 5.10.12) allows an authenticated content editor to plant malicious JavaScript that executes in the Control Panel session of a higher-privileged user who views the affected element index. The flaw lives in the Generated Fields feature, which disables Twig autoescaping and caches field values without encoding, so injected markup is served raw; exploitation requires an editor-level account (PR:L), the optional Generated Fields feature to be in use, and the victim to open the index (UI:P), and the resulting impact is confined to the victim's browser session with no server-side confidentiality, integrity, or availability loss. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the practical risk is moderate rather than critical because of the account, feature, and interaction prerequisites.
Stored and reflected cross-site scripting in djust (pip package djust) before 1.0.7 allows a javascript: URL supplied through user-controllable data to survive into the href/action attributes of built-in component template tags, executing script in a victim's authenticated browser session when the link is clicked. Only applications that bind untrusted URLs to components such as breadcrumb, dj_nav link/dropdown/brand, citation URL, cookie-consent privacy link, error-page action or form action are affected; default djust output is not exposed. The issue is developer-usage-conditional, the assessed vector is CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N (user interaction required, low-privileged/authenticated injecting party), no public exploit identified at time of analysis, and the vendor fix is available in djust 1.0.7.
Span attribute length limits can be bypassed in the OpenTelemetry-Go SDK trace package from 1.10.0 up to (but not including) 1.33.0, allowing an attacker who controls content recorded as a span attribute to retain string values far longer than the configured AttributeValueLengthLimit and thereby inflate per-span memory use inside the instrumented process. The root cause is a Unicode handling defect: the truncation helper misclassifies the valid replacement character U+FFFD as invalid UTF-8 and returns the original oversized value, and a fallback sanitization pass also leaves it unchanged. The impact is limited to a weakening of the SDK's built-in denial-of-service guard - there is no code execution, no confidentiality or integrity impact, and no public exploit code identified at time of analysis; the vendor scores it 5.1 (CVSS 4.0, AV:L, PR:N, VA:L) and our independent assessment is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
Denial of service in HP's HPLIP (HP Linux Imaging and Printing Software) printing stack is reachable when a physically-present attacker supplies specially crafted input that triggers a CWE-191 integer underflow, crashing or hanging affected components; the scored CVSS:3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) limits impact to availability only, with no confidentiality or integrity loss. The physical attack vector (direct hardware/USB or local physical access) is the dominant gating factor and rules out remote or network-based exploitation, and no public exploit has been identified at time of analysis. HP has stated that it identified and remediated the underlying issues, so a vendor fix is available per advisory hpsbpi04151, though the specific affected and fixed version ranges are not enumerated here and must be confirmed against that bulletin. Overall this is a genuine but low-priority issue: real availability impact, but exploitation requires an attacker to already have hands on the machine.
Denial of service in HP Linux Imaging and Printing Software (HPLIP) can be triggered by a physically present attacker who supplies crafted input via a local device or print/scan job, exploiting improper array index validation (CWE-129). Although HP's advisory bundles several vulnerabilities that could potentially enable a broader range of impacts, the specific vector for this CVE limits the effect to availability (system crash or service disruption) with no confidentiality or integrity impact. No public exploit code or active exploitation has been identified at time of analysis, and the primary prerequisite is physical access to the target system.
Local attackers with valid credentials on Linux systems running HPLIP can exploit symbolic-link handling flaws (CWE-61) in HPLIP components to read or modify arbitrary files, as described in HP security bulletin HPSBPI04151. This CVE is one of multiple issues remediated by HP in HPLIP and is assessed as a moderate, locally-scoped issue (CVSS 3.1: AV:L/AC:L/PR:L/UI:N, limited confidentiality/integrity impact) rather than an urgent priority, despite the broader impact list in the description; no public exploit code or CISA KEV active exploitation has been identified at time of analysis. Exploitation requires local access and a vulnerable HPLIP component that follows attacker-controllable symlinks at a predictable path, limiting impact to unauthorized file read/modification.
SQL injection in the REST API of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector lets a remote attacker who already holds valid administrative credentials inject SQL statements through insufficiently validated parameters and read information from the monitoring database. The vulnerability affects ISE and ISE-PIC releases 3.1.x through 3.5.x and carries a CVSS 3.1 base score of 4.9 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N), meaning the impact is limited to confidentiality with no integrity or availability effect. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); the dominant limiting factor is the high-privilege prerequisite, so realistic exposure is confined to insiders, stolen-credential scenarios, or post-compromise abuse by an already-privileged actor.
Authenticated administrators of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) can delete arbitrary files and directories on the underlying operating system by sending a crafted request to the file management function of the web-based management interface. The flaw is a directory traversal (CWE-22) issue in which traversal sequences in a user-supplied file path are not properly validated before the request is processed; exploitation is network-reachable and low-complexity but strictly requires valid administrative credentials (CVSS:3.1/AV:N/AC:L/PR:H/UI:N), which is the primary limiting factor and rules out unauthenticated abuse. Cisco rates this CVSS 4.9 and our independent assessment tracks that as a genuinely lower-priority issue for most environments; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV).
XML external entity (XXE) injection in the offline profiler feed service of Cisco Identity Services Engine (ISE) allows an authenticated remote administrator to read arbitrary files from the appliance and to use it as a pivot for requests to internal systems. The flaw affects ISE and ISE Passive Identity Connector releases across the 3.1 through 3.5 trains, and exploitation requires high-privilege administrative credentials (CVSS 3.1 vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, score 4.9) plus the ability to upload a crafted offline feed package through the administrative interface. Cisco is the reporting vendor and a consolidated advisory is available; no public exploit code and no confirmed active exploitation have been identified at time of analysis, and the high privilege prerequisite keeps the issue bounded to a Medium risk rating.
Authenticated Cisco Identity Services Engine (ISE) administrators who hold delegated management rights over network users can abuse the platform's user-export function to read records - including normally hidden user passwords - belonging to security groups they are not assigned to, because the files backing that export lack proper authorization enforcement. The issue affects ISE 3.1 through 3.5 (and equivalent ISE-PIC deployments) at the patch levels enumerated in the Cisco advisory, and requires a valid high-privileged account with user-management delegation plus access to the web-based management interface; unauthenticated, read-only, or otherwise unprivileged users cannot trigger it. Impact is limited to confidentiality (C:H, no integrity or availability effect, CVSS 4.9 / PR:H), and no public exploit code or confirmed active exploitation was identified at time of analysis. This is a genuine but tightly-gated confidentiality issue rather than a broad emergency, and should be prioritized behind perimeter-critical exposures while still being remediated promptly because the disclosed data includes credentials.
File disclosure in Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) allows a remote attacker who already holds high-privilege administrative access to the management API to read files on the underlying operating system by sending a crafted XML request to a vulnerable API endpoint that fails to restrict external entity references (CWE-611). Cisco scored the issue CVSS 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N); read scope is confined to files the ISE process itself can access, and there is no integrity or availability impact. The dominant limiting factor is the PR:H administrator-credential prerequisite, which makes this a trusted-insider or post-credential-compromise concern rather than a pre-auth remote threat; no public exploit code and no evidence of active exploitation (not listed in CISA KEV) were identified at time of analysis.
Authenticated attackers holding administrative-level privileges on the Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) web-based management interface can write files to arbitrary locations on the underlying system by uploading a crafted file whose supplied path contains directory-traversal sequences, tracked as CVE-2026-76432. The flaw is rated CVSS 4.9 (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N per the vendor and our independent assessment), so the impact is limited to integrity and the practical barrier is the requirement for a valid admin session - attackers must already hold or hijack an administrative account. Affected releases span ISE and ISE-PIC 3.1 through 3.5; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated administrative users of Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) can exploit insufficient input validation in affected APIs to perform SQL/HQL injection, enabling them to view or modify unauthorized database data, with a high integrity impact and low confidentiality impact. The vulnerability affects ISE/ISE-PIC versions 3.1 through 3.5 and requires valid administrative credentials; no public exploit identified at time of analysis.
Authenticated path traversal in the certificate import function of the Cisco ISE and Cisco ISE-PIC web-based management interface lets a remote attacker who already holds valid administrative credentials read arbitrary files from the appliance, exposing configuration data and other sensitive content. Exploitation requires high-privileged access (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, base score 4.9), which meaningfully constrains the threat: the attacker must first compromise or be granted an administrative account, so this is best treated as a post-compromise information-disclosure and privilege-escalation enabler rather than an unauthenticated entry point. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV). This is a moderate, not urgent, priority, with the practical exposure concentrated on installations where the management interface is reachable from broader networks and admin credentials are loosely governed.
SQL and HQL injection in the management APIs of Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) allows an authenticated, high-privileged administrator to execute arbitrary SQL or Hibernate Query Language statements against the product's underlying database, enabling access to or modification of data the attacker is not authorized to view or change. The flaw (CWE-564) stems from insufficient validation of user-supplied input passed to APIs that build database queries, and is reachable over the network without user interaction against affected 3.1 through 3.5 release trains; exploitation requires valid administrative credentials (CVSS 3.1 PR:H), which is the principal limiting factor. Cisco's advisory scores this 4.9 (Medium) using CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N, while the independent assessment rates confidentiality and integrity impact as High; no public exploit has been identified at time of analysis and there is no CISA KEV listing.
Authenticated remote attackers holding valid administrative credentials can read sensitive data - including hashed credentials usable in follow-on attacks - from Cisco Identity Services Engine (ISE) by sending a single crafted API request that is improperly validated and reaches the backend as SQL (CWE-89). The flaw affects ISE Software across the 3.1.x, 3.2.x, 3.3.x, 3.4.x and 3.5 branches at numerous patch levels; exploitation requires administrator-level privileges (PR:H) but no user interaction, and the API is network-reachable. Cisco's own CVSS of 4.9 (Medium) is a credible ceiling rather than an understatement, because the high-privilege prerequisite sharply limits who can trigger it; no public exploit code or confirmed active exploitation was identified at time of analysis.
SQL and HQL injection in Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) allows an authenticated, remote user with valid administrative credentials to submit crafted requests to affected APIs and run arbitrary SQL or HQL statements against the product's underlying database, giving them the ability to read or alter data they are not authorized to access. The vulnerability is rated CVSS 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N per independent assessment), with the high privilege requirement (PR:H) and the low confidentiality but high integrity impact being the defining characteristics; the affected code spans the 3.1, 3.2, 3.3, 3.4 and 3.5 release trains. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so the primary risk is insider or post-compromise abuse of administrative access rather than opportunistic external exploitation.
SQL and HQL injection in Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) lets an authenticated remote attacker with administrative credentials execute arbitrary database queries against the underlying data store, potentially reading or modifying data outside their authorization. The flaw stems from insufficient validation of user-supplied input to affected management APIs before it is used to construct database queries, and it is exploitable over the network without user interaction (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N per independent assessment). The high-privilege prerequisite is the main limiting factor: no public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS probability was supplied, making this a genuine but low-urgency issue for most deployments.
SQL injection in the REST APIs of Cisco Identity Services Engine (ISE) and the ISE Passive Identity Connector (ISE-PIC) allows an attacker who already holds valid administrative credentials to read information from the session database, with no integrity or availability impact. The vector is network-reachable, low complexity, and requires no user interaction, but the PR:H prerequisite confines this to a post-authentication data-disclosure/escalation concern rather than an initial-access vector. No public exploit code has been identified at time of analysis and there is no evidence of active exploitation; given the administrative credential requirement and read-only impact, this is a lower-priority issue despite the criticality of the affected product.
Remote, authenticated administrators of Cisco Identity Services Engine (ISE) can escalate from the web management interface to write access on the appliance's underlying operating system by sending a single crafted HTTP request, and Cisco confirms root is easy to reach from that primitive, making the practical outcome full device compromise. The flaw is improper restriction of resource/file names (CWE-641) in the ISE management web/API layer, reachable over the network with no user interaction but requiring valid administrative credentials (CVSS 3.1 PR:H), so it is a post-authentication escalation path rather than a pre-auth entry point. Cisco's published base score of 4.9 (Medium) understates the outcome - the vendor assigned a High Security Impact Rating for exactly this reason, and our independent assessment raises confidentiality, integrity and availability impact to High; no public exploit code has been identified at time of analysis and the CVE is not in CISA KEV.