Authentication Bypass

Oracle WebCenter Portal 12.2.1.4.0 and 14.1.2.0.0 ship a flaw in the Runtime Tools component that lets any authenticated low-privileged user read critical portal data and partially degrade portal availability over HTTP. Oracle rates it as easily exploitable (CVSS 7.1, AV:N/AC:L/PR:L/UI:N, C:H/A:L), so no user interaction and no administrative role is needed beyond a valid account. No public exploit code and no CISA KEV entry were identified at time of analysis, but the data-exposure impact on an enterprise portal makes it worth prompt patching.

Oracle WebCenter Portal 12.2.1.4.0 and 14.1.2.0.0 contain an easily exploited authorization flaw in the Runtime Tools component that lets a low-privileged, network-connected user reach and manipulate data well outside their intended scope, including data belonging to connected products (CVSS 8.5, scope change, high confidentiality and low integrity impact). Exploitation requires only a valid low-privilege portal account and standard HTTP access — no user interaction — making it attractive for lateral movement inside enterprise portal deployments. There is no public exploit identified at time of analysis, and no CISA KEV listing or EPSS score was supplied in the available intelligence.

Oracle XML Gateway, the E-Business Suite module that exchanges XML business documents with external trading partners, exposes critical data to any low-privileged user who can reach its HTTP endpoints in versions 12.2.3 through 12.2.15. A successful attack gives the intruder read access to data they should not see — described by Oracle as unauthorized access to critical data or complete access to all XML Gateway accessible data — and also allows a partial denial of service that degrades the module's availability. The flaw is trivially reachable (network vector, low complexity, no user interaction), and no public exploit code has been identified at the time of analysis.

Authentication bypass in the OIM Legacy UI component of Oracle Identity Manager 12.2.1.4.0 and 14.1.2.1.0 lets an unauthenticated attacker who can reach the interface over HTTP take full control of the affected deployment, with complete loss of confidentiality, integrity, and availability (CVSS 3.1 base score 9.8). Exploitation requires no credentials or user interaction (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but it does depend on the Legacy UI being network-reachable; instances shielded by segmentation, VPN, or reverse-proxy access controls that block direct HTTP to that component are not exposed to external actors. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and affected versions are strictly limited to 12.2.1.4.0 and 14.1.2.1.0.

Oracle WebCenter Portal 12.2.1.4.0 and 14.1.2.0.0 allow a low-privileged, authenticated attacker with HTTP network access to read data they should not be able to reach through the Portlet Services component, scoring 7.7 on CVSS 3.1 with a scope change that can extend the impact to interconnected products. Exploitation requires only a valid low-privilege account and no user interaction, but with no CISA KEV listing, no EPSS score, and no public exploit code identified in the supplied intelligence, there is currently no public exploit identified at time of analysis. The practical priority is for organizations running the two affected WebCenter Portal releases facing untrusted or multi-tenant user populations.

Unauthenticated remote attackers can achieve full takeover of Oracle WebCenter Sites 12.2.1.4.0 and 14.1.2.0.0 through an authentication bypass reachable over HTTP, per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H vector that drives the 9.8 base score. No authentication, user interaction, or non-default configuration is required - the only practical prerequisite is network reachability of the WebCenter Sites HTTP interface, which means internet-exposed authoring or delivery instances carry the highest risk. The flaw is rated CWE-287 (Improper Authentication), and at time of analysis there was no public exploit code identified and no confirmed active exploitation (not listed in CISA KEV); Oracle has published a Critical Security Patch Update advisory covering the affected versions.

Authentication bypass in Oracle WebCenter Sites 12.2.1.4.0 and 14.1.2.0.0 lets unauthenticated remote attackers reach and compromise the application purely over HTTP, with a successful exploit resulting in complete takeover of the WebCenter Sites instance (CVSS 3.1 base score 9.8, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Per the assessed vector there are no prerequisites beyond network reachability to the affected service: no credentials, no user interaction, and low attack complexity, which Oracle itself characterizes as 'easily exploitable.' No public exploit code has been identified at time of analysis, and no CISA KEV listing or EPSS score was supplied in the available intelligence, so the immediate driver for prioritization is the 9.8 severity combined with unauthenticated network exploitability rather than confirmed active exploitation.

An authentication bypass in Oracle WebCenter Sites 12.2.1.4.0 and 14.1.2.0.0 enables unauthenticated remote attackers to take over the application via HTTP requests, rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with full confidentiality, integrity and availability impact. The vulnerability sits in the WebCenter Sites component of Oracle Fusion Middleware and requires no credentials, no user interaction and no non-default configuration - only network reachability of the HTTP service - making any internet-exposed instance an immediate target. No public exploit code and no confirmed active exploitation were identified at time of analysis (no CISA KEV listing), but the trivial attack prerequisites mean exposed deployments should be treated as urgent; instances confined to internal networks or sitting behind an authenticating reverse proxy or WAF have materially reduced reachable attack surface.

Unauthenticated attackers with HTTP network access to Oracle WebCenter Sites 12.2.1.4.0 and 14.1.2.0.0 can read data they should not be able to reach, including potentially all content and data the application can access. Oracle rates it 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N), meaning no credentials, no user interaction and no special complexity are needed - only reachability to the web interface. There is no public exploit code and no CISA KEV listing at time of analysis, but the low attack requirements and high confidentiality impact make it a strong patch-now candidate for any internet-facing deployment.

Oracle Managed File Transfer (MFT) Runtime Server, the file-transfer component of Oracle Fusion Middleware, allows an authenticated low-privileged attacker with network HTTP access to create, delete, modify, and read critical data handled by MFT, and the scope change (S:C) means a successful attack can escape the MFT trust boundary and impact additional Oracle products. The flaw is trivially reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, base 9.6), requiring no user interaction, but it is not pre-authentication: the attacker must already hold valid low-privileged credentials and be able to reach a MFT Runtime Server HTTP endpoint on versions 12.2.1.4.0 or 14.1.2.0.0. There is no public exploit identified at time of analysis and no evidence of confirmed active exploitation (no CISA KEV listing); the 9.6 score reflects the confidentiality/integrity impact and cross-boundary scope change rather than observed exploitation, and the Oracle advisory provides no technical root-cause detail or CWE.

Unauthenticated attackers on the same adjacent network segment can compromise the Oracle Identity Manager Connector (versions 12.2.1.4.0 and 14.1.2.1.0), bypassing authentication to gain unauthorized read/write access to critical data, with scope change potentially affecting other Oracle products. This high-severity vulnerability (CVSS 9.3) requires local network adjacency but no credentials or user interaction. No public exploit code or active exploitation has been identified at time of analysis.

Authentication bypass in the Core component of Oracle Identity Manager Connector 12.2.1.4.0 and 14.1.2.1.0 allows a remote, unauthenticated attacker who can reach the connector's TCP listener to read and modify the identity data it manages, with Oracle explicitly noting the attack may also significantly impact connected downstream products (scope change). Oracle scores it 8.7 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N) while describing it as difficult to exploit, so the flaw is reachable without credentials but is not trivially automatable. The supplied intelligence contains no EPSS score, no CISA KEV entry, and no evidence of public exploit code at time of analysis.

Unauthenticated remote attackers can read critical data from the Oracle Identity Manager Connector (Core component) in versions 12.2.1.4.0 and 14.1.2.1.0 by sending crafted HTTP requests, with no authentication or user interaction required. Oracle scores the flaw CVSS 8.6 (AV:N/AC:L/PR:N/UI:N) and classifies it as an authentication bypass with high confidentiality impact only; the scope-change metric means a successful attack can also expose downstream products that the connector reaches. No public exploit code or active exploitation is identified at time of analysis, and EPSS data was not provided, so real-world aggressiveness cannot be quantified.

Unauthenticated remote attackers can achieve full takeover of Oracle WebLogic Server 12.2.1.4.0, 14.1.1.0.0, and 14.1.2.0.0 by exploiting an authentication bypass in the Web Container component reachable over HTTP. The vulnerability carries a CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), meaning no credentials, user interaction, or special preconditions are required beyond network reachability to the WebLogic HTTP listener; the Scope:Changed rating indicates successful exploitation can also compromise additional products beyond WebLogic itself. There is no public exploit identified at time of analysis and no confirmed active exploitation (no CISA KEV listing), but the trivial attack preconditions and maximum severity rating make this a top-priority patch target for any internet-exposed deployment.

Unauthenticated remote attackers can achieve full takeover of Oracle Platform Security for Java (OPSS) versions 12.2.1.4.0 and 14.1.2.0.0, an authentication-bypass flaw (CWE-287) in the Centralized Thirdparty Jars component of Oracle Fusion Middleware that carries a maximum CVSS 3.1 base score of 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Because the scope is marked as changed (S:C), Oracle warns that a successful compromise of OPSS - the shared security services layer that other Fusion Middleware components depend on - may significantly propagate impact to additional products, which is what elevates this above the otherwise near-identical 9.8-rated issue. No public exploit code has been identified and there is no CISA KEV listing at time of analysis, but Oracle characterises the flaw as 'easily exploitable' with no privileges or user interaction required, so the practical limiting factor is whether the affected middleware's HTTP surface is network-reachable - internet-exposed deployments are at the highest risk.

Oracle PeopleSoft Enterprise PeopleTools versions 8.61 through 8.63 expose an exploitable flaw in the SQR component that lets a low-privileged, authenticated user reach the service over HTTP and read data well beyond their intended authorization while also crashing or repeatedly hanging the application. Per the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H) the attacker needs a valid account but no elevated role and no victim interaction, and the confidentiality impact is rated total for data accessible through PeopleTools, with a matching high availability impact from the resulting denial of service. Oracle rates this 8.1 and released it in its Critical Security Patch Update cycle; no EPSS score, CISA KEV listing, or public exploit code was supplied with the source data at time of analysis.

Oracle WebCenter Enterprise Capture 12.2.1.4.0 and 14.1.2.0.0 (Fusion Middleware, Client Bundle component) can be abused by a high-privileged, network-positioned attacker who convinces a second user to interact with a crafted HTTP request, yielding read, creation, modification, and deletion access to critical capture data. Because the CVSS vector carries a scope change (S:C), the impact is not confined to Enterprise Capture itself and can extend to other Fusion Middleware components reachable from the affected deployment. There is no indication of public exploit code or confirmed active exploitation, and no EPSS score was supplied with the source data, so the practical urgency rests mainly on the 8.1 severity, the scope change, and the sensitivity of captured document data.

Low-privileged authenticated users with network access can exploit a flaw in the Client Bundle component of Oracle WebCenter Enterprise Capture 12.2.1.4.0 and 14.1.2.0.0 to read critical data and modify records, with the impact extending beyond the vulnerable product itself (scope change). Oracle rates the issue CVSS 3.1 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N), driven by high confidentiality impact and cross-component scope change rather than by availability or integrity loss. No public exploit code and no evidence of active exploitation were identified at time of analysis, and no EPSS or CISA KEV data was supplied with the source material.

A difficult-to-exploit flaw in the Client Bundle component of Oracle WebCenter Enterprise Capture (12.2.1.4.0 and 14.1.2.0.0) lets an attacker who already holds a low-privileged logon on the host compromise the application, reading and altering critical capture data and potentially affecting interconnected downstream products through a scope change. Exploitation is not trivial: it requires local access, a low-privileged account, high attack complexity, and a second user to perform an interaction. No public exploit code has been identified and the issue is not listed in CISA KEV at time of analysis; Oracle's Critical Security Patch Update advisory is the authoritative source.

Improper authorization on the SOAP-facing Client Bundle interface of Oracle WebCenter Enterprise Capture 12.2.1.4.0 and 14.1.2.0.0 lets a low-privileged, network-positioned attacker read all data the application can reach and modify a subset of it. Oracle scores it 8.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N), and the Changed scope metric indicates the blast radius can extend beyond Capture into other Fusion Middleware components. No public exploit code or CISA KEV entry was identified at time of analysis; the Oracle Critical Security Patch Update advisory (cspusep2026) is the authoritative source.

Improper authentication in the Messaging Enabler component of Oracle Fusion Middleware Service Delivery Platform allows unauthenticated remote attackers to bypass authentication and fully take over the product, compromising confidentiality, integrity, and availability. Affected releases are Oracle SDP 12.2.1.4.0 and 14.1.2.0.0, and per the assessed CVSS vector (AV:N/AC:L/PR:N/UI:N) exploitation requires only network reachability to the Messaging Enabler HTTP interface - no credentials, privileges, or user interaction are needed. There is no public exploit code identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); the main real-world limiting factor is exposure, since SDP is niche carrier/telecom middleware typically deployed inside operator networks rather than on the public internet.

Authentication bypass in Oracle Platform Security for Java (OPSS) 12.2.1.4.0 and 14.1.2.0.0 allows unauthenticated remote attackers to reach the affected SOAP interface and achieve full takeover of the OPSS instance, with high confidentiality, integrity, and availability impact (CVSS 9.8). The flaw is classified as CWE-287 improper authentication and is tagged as an authentication bypass; per the Oracle-supplied CVSS vector, no credentials or user interaction are required. No public exploit identified at time of analysis, but any reachable vulnerable OPSS service should be treated as high risk because the practical limiting factor is network exposure of the SOAP endpoint rather than a configuration prerequisite.

Unauthenticated remote attackers who can reach an exposed LDAP authentication path in Oracle Platform Security for Java (OPSS) can achieve complete takeover of the OPSS security framework in Oracle Fusion Middleware versions 12.2.1.4.0 and 14.1.2.0.0, with full confidentiality, integrity and availability impact (CWE-287 improper authentication, CVSS 9.8, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The flaw sits in the Centralized Thirdparty Jars component and requires no credentials and no user interaction, but exploitability in practice depends on network reachability: OPSS is an embedded security framework consumed by Fusion Middleware applications rather than a standalone internet-facing service, so internal-only or firewalled OPSS/LDAP endpoints substantially reduce exposure. No public exploit code and no CISA KEV entry were identified at time of analysis, and no real-world exploitation telemetry is available, so the 9.8 severity reflects assessed potential rather than observed attack activity.

Oracle PeopleSoft Enterprise PeopleTools versions 8.61 through 8.63 contain a flaw in the Business Interlink component that lets a low-privileged, network-reachable user read or fully compromise PeopleTools-accessible data and modify or delete some of it, with impact extending to other connected products (scope change). Oracle rates it CVSS 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N) and notes it is 'easily exploitable' by a low-privileged attacker over HTTP. No EPSS score, CISA KEV listing, or public proof-of-concept was present in the supplied intelligence, so active exploitation is not confirmed at time of analysis.

Unauthenticated remote attackers who can reach the Portlet Services component of Oracle WebCenter Portal 12.2.1.4.0 or 14.1.2.0.0 over HTTP can bypass authentication and achieve full takeover of the application, with complete confidentiality, integrity and availability impact (CVSS 3.1 base 9.8; vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The flaw is an improper-authentication defect (CWE-287) and, per the assessed vector, needs no credentials, no user interaction and no non-default configuration, so any instance with Portlet Services reachable is directly at risk. No public exploit code has been identified at time of analysis, and the principal real-world limiter is exposure, since WebCenter Portal is typically deployed behind an enterprise perimeter rather than openly on the internet; this is nevertheless a high-priority issue on every available static signal, with thin real-world exploitation evidence.

Authenticated attackers holding a low-privileged account can exploit the Authentication Engine in Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0 over HTTPS to read, create, delete, or modify all data reachable through the service, with CVSS 3.1 base score 9.6 reflecting high confidentiality and integrity impact and a scope change. The flaw is remotely reachable with low attack complexity and no user interaction, but it is not pre-authentication: a valid low-tier credential on the OAM instance is required, which is the main limiting factor on exploitation. No public exploit identified at time of analysis, and the vulnerability is not listed as confirmed actively exploited (CISA KEV); Oracle's Critical Patch Update advisory at https://www.oracle.com/security-alerts/cspusep2026.html is the authoritative source.

Unauthenticated takeover of Oracle JDeveloper is possible in supported versions 12.2.1.4.0 and 14.1.2.0.0 through the ADF Faces component, which is exposed over HTTP; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) confirms remote, unauthenticated, low-complexity exploitation requiring no user interaction, with full confidentiality, integrity, and availability impact. The root cause is an authentication bypass (CWE-287) rather than a memory-safety or injection flaw, meaning an attacker who can reach the ADF Faces web tier may be able to act with privileges they were never granted. No public exploit code has been identified at time of analysis and the vulnerability is not listed as confirmed actively exploited (CISA KEV); the main real-world constraint is network exposure, since JDeveloper is primarily a Java development IDE and its ADF Faces web tier is not normally published to untrusted networks.

Oracle WebCenter Portal 12.2.1.4.0 and 14.1.2.0.0 can be taken over by an unauthenticated remote attacker who reaches the Composer component over HTTP, because the component fails to properly enforce authentication (CWE-287). Oracle scores this 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no credentials, user interaction, or non-default configuration are required - only network reachability of the WebCenter Portal HTTP interface, with the stated outcome being full takeover of the portal. At time of analysis there is no public exploit identified and the issue is not listed as confirmed actively exploited (CISA KEV), so the practical risk is driven by exposure: internet-facing instances are directly at risk, while deployments confined to internal networks or sitting behind an authenticating reverse proxy or WAF are materially harder to reach. This is assessed as well-calibrated maximum severity rather than an inflated score, since an unauthenticated authentication bypass leading to product takeover justifies the C:H/I:H/A:H impact set.

Improper handling of chart content in the Charting component of Oracle PeopleSoft Enterprise PeopleTools 8.61 through 8.63 lets a low-privileged, authenticated attacker read and modify critical application data after inducing another user to interact with a crafted HTTP request. Successful exploitation yields high confidentiality and integrity impact across all data the victim's session can reach, though availability is unaffected. No public exploit code has been identified at time of analysis, no CISA KEV listing is present in the supplied data, and no EPSS score was provided.

Authentication bypass in the Portlet Services component of Oracle WebCenter Portal 12.2.1.4.0 and 14.1.2.0.0 lets unauthenticated remote attackers reach protected functionality over HTTP and, on success, take over the application (CVSS 3.1 base score 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The flaw maps to CWE-287 (Improper Authentication), meaning the portal's Portlet Services layer fails to properly validate that a request originates from an authenticated session. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited; the main exposure driver is network reachability of the WebCenter Portal HTTP interface, so internet-facing or broadly reachable instances behind no WAF or proxy carry the highest risk. Oracle addresses it in the September 2026 Critical Patch Update.

Improper authentication in the Portlet Services component of Oracle WebCenter Portal allows unauthenticated attackers with HTTP network access to the portal to bypass authentication and gain read and write access to all portal-accessible data, including the ability to create, delete, or modify critical content. Only versions 12.2.1.4.0 and 14.1.2.0.0 of this Oracle Fusion Middleware product are affected, and the flaw is rated high severity (CVSS 3.1 base 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) with no availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, so exploitation risk is driven primarily by internet or broad-network exposure of an unpatched portal.

Authentication bypass in the Oracle Access Manager (Fusion Middleware) Authentication Engine lets unauthenticated remote attackers with HTTP network access compromise OAM instances running 12.2.1.4.0 or 14.1.2.1.0, resulting in complete takeover of the affected service with high confidentiality, integrity and availability impact (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Successful exploitation of the CWE-287 flaw effectively grants the attacker the identity and authorization context the Authentication Engine is supposed to enforce, so any downstream application trusting OAM for single sign-on or access decisions is exposed to the same session. At the time of analysis there is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified; the practical exposure is driven almost entirely by the network reachability of the OAM Authentication Engine endpoint, with internet-facing gateways the highest priority to patch.

Authentication bypass in Oracle Access Manager 12.2.1.4.0 and 14.1.2.0.0 lets an unauthenticated, network-positioned attacker take over the affected Access Manager instance, rated CVSS 3.1 9.8 (CWE-287, Improper Authentication) with high confidentiality, integrity, and availability impact. The vulnerable component is the Authentication Engine itself, and the vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) confirms no credentials, privileges, or user interaction are required, so any HTTP-reachable OAM deployment of those two versions is a candidate entry point. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); however, Oracle characterizes it as easily exploitable, so internet-exposed OAM instances should be treated as urgent.

Unauthenticated remote attackers can bypass authentication in Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0, gaining full read and write access to all data managed by the affected component. This easily exploitable vulnerability (CVSS 9.1) requires only network access to the OAM authentication engine over HTTP and no credentials or user interaction. No public exploit code or active exploitation has been observed at the time of analysis, but the lack of authentication and high impact make it a critical risk for exposed instances.

Improper access control in the OIM Legacy UI component of Oracle Identity Manager (12.2.1.4.0 and 14.1.2.1.0) lets a network-positioned attacker who already holds a highly privileged account read and alter identity and provisioning data, with a scope change that can cascade into other connected Oracle products. Oracle rates it 7.6 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N), so exploitation is trivial once administrative access is obtained but is gated by that high-privilege requirement. No CISA KEV listing, public exploit code, or EPSS score was supplied with this record, so active exploitation is not confirmed (no public exploit identified at time of analysis).

Unauthenticated attackers with network access to Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0 can compromise the Authentication Engine component over HTTP, obtaining unauthorized read access to critical data or all data accessible through the product. Oracle rates this CVSS 3.1 8.6 with a scope change (S:C), meaning affected deployments can be leveraged to significantly impact downstream/connected applications that trust OAM identities. At time of analysis there is no public exploit code identified and no CISA KEV listing, but the attack is trivially automatable (AV:N/AC:L/PR:N/UI:N), so internet-exposed OAM consoles and SSO endpoints should be treated as high priority.

Unauthenticated network attackers who can reach the T3 or IIOP listener fronting Oracle Access Manager's Authentication Engine on versions 12.2.1.4.0 or 14.1.2.1.0 can bypass authentication and take full control of the component, yielding complete loss of confidentiality, integrity, and availability (CVSS 3.1 base 9.8, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). No credentials or user interaction are required; the only meaningful precondition is that the T3/IIOP protocols are reachable from the attacker's position, so deployments that restrict those protocols to trusted internal networks are not externally exploitable. This vulnerability is not listed in CISA KEV and no public exploit code has been identified at time of analysis, but the combination of a perfect-exploitability CVSS vector, an authentication-bypass root cause, and default-exposed WebLogic remoting protocols makes it a high-priority patch target.

Oracle Access Manager versions 12.2.1.4.0 and 14.1.2.1.0 contain a flaw in the Authentication Engine component that lets a high-privileged, network-positioned attacker read, create, delete, or modify data managed by the OAM deployment — and because the flaw crosses a security scope boundary, downstream applications that trust OAM for identity can be affected as well. The CVSS 3.1 base score is 8.7 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N), reflecting an easily triggered but credentialed attack with high confidentiality and integrity impact and no availability impact. No public exploit code, EPSS score, or CISA KEV listing is present in the supplied intelligence, so it is treated as not yet publicly exploited at time of analysis; Oracle ships fixes through its Critical Patch Update / Security Alert program referenced in the advisory link.

Authentication weaknesses in the Oracle Access Manager Authentication Engine expose deployments running 12.2.1.4.0 and 14.1.2.1.0 within Oracle Fusion Middleware: an attacker with network access over HTTP and only a low-privileged foothold can bypass or subvert authentication to create, delete, or modify critical data and read data across the OAM-accessible estate, while also degrading service availability. Because the CVSS vector carries a scope change (S:C), a compromise of OAM can propagate to other products that rely on it as their single sign-on and identity provider, which is what pushes the base score to 9.9 rather than the more typical 8.x for an authenticated-only flaw. No user interaction is required and attack complexity is low, though the PR:L rating means the attacker must already hold at least minimal valid access or be able to reach an authenticated interface - this is not a fully unauthenticated pre-auth bypass. There is no CISA KEV listing and no public exploit code identified in the available intelligence, so exploitation is not confirmed actively exploited (CISA KEV) and no public exploit identified at time of analysis.

Authentication bypass in Oracle Access Manager 12.2.1.4.0 and 14.1.2.1.0 lets an unauthenticated remote attacker with HTTP network access compromise the product's Authentication Engine and take over the affected instance. Rated CVSS 3.1 base 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), the scope-change flag means a successful compromise propagates to downstream applications that trust OAM for authentication, widening impact well beyond the OAM host itself. No public exploit has been identified at time of analysis, but the pre-auth, network-reachable attack path makes this a top-tier priority for any organization running the two named versions.

Unauthenticated, network-positioned attackers can fully take over Oracle Identity Manager 12.2.1.4.0 and 14.1.2.1.0 by bypassing authentication in the Core component (CVE-2026-70913), which carries a CVSS 3.1 base score of 9.8 using the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Oracle characterizes the flaw as easily exploitable over HTTP, meaning no credentials, no user interaction, and no non-default configuration are required - only HTTP reachability to an affected instance - and successful exploitation gives complete loss of confidentiality, integrity, and availability on the identity platform. No public exploit code or confirmed active exploitation was identified at time of analysis, but the zero-prerequisite exploitation profile makes any internet- or broadly reachable OIM deployment a top-priority exposure.

Unauthenticated remote takeover of Oracle WebLogic Server is achievable through its T3 and IIOP protocol listeners in versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. Classified as CWE-287 (Improper Authentication) and scored CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw allows any network-reachable attacker - no credentials, no user interaction - to gain full confidentiality, integrity, and availability impact over the affected server, which Oracle itself rates 'easily exploitable'. Exploitation hinges on reachability of the T3/IIOP listeners, which are enabled by default on the WebLogic administration and managed-server listen ports, meaning most standard deployments are exposed unless those protocols are filtered, disabled, or network-segmented; no public exploit code or confirmed in-the-wild activity was identified at time of analysis, so exposure should be treated as high-impact and high-priority but not yet observed as actively exploited.

Authentication bypass in Oracle WebLogic Server (Core component) allows unauthenticated, network-positioned attackers to gain full takeover of the server, earning the maximum CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with complete confidentiality, integrity, and availability impact. All four supported branches are affected: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. Exploitation requires reachability of the T3 or IIOP protocol listener (commonly port 7001) with no authentication and no user interaction, and no public exploit code has been identified at time of analysis; the CVE is not listed in CISA KEV, so exposure is primarily governed by whether T3/IIOP is reachable from untrusted networks.

Unauthenticated remote takeover of Oracle WebLogic Server is achievable via the T3 and IIOP listeners in versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0, where an improper-authentication defect (CWE-287) in the Core component of Oracle Fusion Middleware lets a network attacker bypass login and obtain full confidentiality, integrity, and availability impact (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The only real precondition is reachability of the T3/IIOP listener, which is enabled by default and usually shares the WebLogic HTTP port (7001); no credentials and no user interaction are required, so environments that firewall, disable, or connection-filter T3/IIOP materially reduce exposure. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, but this is a genuine high-priority vulnerability rather than a CVSS-inflated one.

Authentication bypass in the Apache Airflow Keycloak provider (apache-airflow-providers-keycloak) before 0.10.0 lets an attacker who holds valid client credentials for any unrelated confidential client in a shared Keycloak realm obtain a signed Airflow session JWT. Because the provider's token endpoint does not allowlist client ids, credentials that were never issued for Airflow are silently accepted as Airflow login credentials, and Airflow mints a session token for that third-party application's service account. Access is then limited only by what that service account can reach plus any endpoint gated solely on being authenticated, and the endpoint additionally permits unauthenticated credential guessing against Keycloak under Airflow's identity. No public exploit code or CISA KEV entry was identified at time of analysis; severity is rated moderate by the vendor, with the impact bounded by subject-level resource authorization.

HTTP request smuggling in http4s Ember (all releases prior to 0.23.35 and 1.0.0-M47) lets an unauthenticated remote attacker bypass front-end proxy controls by sending duplicate Content-Length headers with differing values, because the Ember HTTP/1.1 parser accepts the conflict and frames the message using the last value instead of rejecting it as a framing error. When Ember runs behind a keep-alive intermediary that selects a different occurrence, the attacker can prepend a smuggled request to a later user's connection, capture that user's headers, or poison a shared cache; the same shared parser can also misframe upstream responses when an http4s client proxies for multiple downstream consumers. No public exploit code or CISA KEV entry was identified at time of analysis, but the CVSS 8.7 scope-changed rating makes this a priority fix for exposed Scala services sitting behind reverse proxies, CDNs, or load balancers.

Request smuggling in the http4s Ember HTTP/1.1 parser lets an unauthenticated, remote attacker bypass front-end access controls, splice a victim request onto an attacker-controlled prefix, or poison a caching layer, but only where ember-server runs as an origin behind a keep-alive intermediary that forwards both Transfer-Encoding and Content-Length headers and frames the body by Content-Length while Ember frames by chunked (a CL.TE mismatch); a standalone Ember server with no fronting proxy is not exploitable, and the client path only desyncs when a malicious or compromised upstream sends both headers over a pooled ember-client connection. The flaw affects http4s-ember-core 0.23.34 and earlier in the 0.23.x line, plus 1.0.0-M1 through 1.0.0-M46, with a parser that fails to treat dual-framed messages as the framing error RFC 9112 §6.1 requires; the vendor-assessed CVSS 4.0 score is 9.2, with the topology dependency captured by the AT:P metric. Fixed in 0.23.35 and 1.0.0-M47 (vendor-released patch); no public exploit identified at time of analysis, and CISA SSVC records exploitation as none.

A permission bypass in the Android Cellular Modem (baseband) component lets an attacker who is within radio range of the device escalate privileges inside the modem context, exposing confidentiality, integrity and availability of device data with no user interaction. Exploitation requires the attacker to already hold low-level privileges on the modem interface (CVSS PR:L) and to be network-adjacent (AV:A), which in practice points to a rogue or compromised cellular base station rather than an internet-based attacker. The flaw stems from a logic error in permission checking rather than a memory-safety bug, and at time of analysis there is no public exploit code and no CISA KEV listing, though the vendor has published a fix in the September 2026 Pixel security bulletin that should be treated as authoritative.

Let me synthesize the analysis for CVE-2026-79993. Key facts: - Apache ZooKeeper deleteContainer opcode (0x14/20) processed without ACL check. - Affected: 3.9.0-3.9.5, 3.8.0-3.8.6. - Fixed in 3.9.6 and 3.8.7. - Any client with plain TCP session on client port 2181, no auth, no ACL permissions, can delete any empty persistent znode (regular persistent, container, TTL nodes). - Skips session check and DELETE ACL check. - Authorization bypass / ACL enforcement bug (CWE-862 Missing Authorization presumably, or CWE-863 Incorrect Authorization). - No CVSS provided, no EPSS, no KEV, no POC. - Credit given. Let me construct fields. Product name: "Apache ZooKeeper" Summary: original synthesis. Start with impact verb + product. "Unauthorized deletion of znodes in Apache ZooKeeper 3.8.x and 3.9.x..." Technical context: ZooKeeper coordination kernel, znodes, ACLs, opcodes, container nodes, TTL nodes. CWE-862/CWE-863. The deleteContainer opcode is internal-only, used by servers to remove container nodes when they become empty. The regular DELETE path (opcode 2) enforces session check and ACL. deleteContainer path skips both. Note: description says "allowing any authenticated client" but then says "with NO authentication and NO ACL permissions". Conflicting. Actually the description contradicts itself: "allowing any authenticated client" vs "with NO authentication". Hmm. The plain TCP session means anyone with network access to port 2181 — no authentication needed. So PR:N effectively. But wait—can they delete any znode? The check is on empty persistent znodes. Actually the description says deleteContainer can delete "any empty persistent znode (including regular persistent nodes, container nodes, and TTL nodes)". So condition: znode must be empty (no children). Actually deleteContainer opcode normally deletes container nodes; here it can delete any empty persistent znode. So prerequisite: target znode must have zero children. CVSS assessment: AV:N, AC:L, PR:N (no auth n

Missing authentication for a critical function in Dell Wyse Management Suite (WMS) releases prior to 2605.0.3.683 allows a remote, unauthenticated attacker to invoke a protected function without supplying credentials, resulting in unauthorized access to the management platform (CWE-306). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 7.5) indicates the flaw is exploitable with no authentication, no user interaction and low complexity, with integrity impact rated High and no confidentiality or availability impact. Dell has published advisory DSA-2026-387 with a fixed build (2605.0.3.683); no CISA KEV entry, EPSS score or public proof-of-concept was provided in the source data, so active exploitation is not confirmed.

Account takeover of non-superuser accounts is possible in Concrete CMS 9.2.0 through 9.5.2 because the REST API user write endpoints (PUT /ccm/api/1.0/users/{uID} and POST /ccm/api/1.0/users/{uID}/change_password) fail to enforce per-field edit_user_properties permissions. An attacker holding an OAuth token scoped for updates and permission to edit only one non-sensitive field on another user can rewrite that user's password, username, email, and attributes, fully seizing the account; superuser accounts are explicitly out of reach. There is no public exploit identified and no CISA KEV listing at time of analysis, so this currently represents a targeted, credential-gated authorization defect rather than a mass-exploitation event. Concrete CMS rated it CVSS v4.0 7.4 (CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N).

Authenticated users of GitLab CE/EE can read CI/CD variables that are scoped to environments they are not entitled to, because the environment scope pattern matcher fails to validate scope input correctly. The flaw affects all versions from 15.7 up to 19.1.7, 19.2.5, and 19.3.1, with fixes in 19.1.8, 19.2.6, and 19.3.2. Public exploit code exists (referenced via a HackerOne report), the issue carries a CVSS of 7.7 with a confidentiality-only, scope-changed profile, and there is no CISA KEV listing indicating confirmed active exploitation at time of analysis.

Bambuddy, a self-hosted print archive and management system for Bambu Lab 3D printers, fails open when its database is unavailable: versions from 0.1.6 up to (but not including) 0.2.4.4 catch every exception in the authentication probe and treat the failure as 'auth disabled', granting unauthenticated access to every protected endpoint. A remote attacker with no credentials can force the condition by flooding the public /api/v1/auth/login endpoint until the process exhausts its file-descriptor budget so the next SQLite connect() raises, then timing requests into that transient window to create a persistent admin account or API key, download the database backup (hashed passwords, encryption keys, printer access codes, MFA secrets), alter settings, or control printers. Vendor/CISA scoring is critical (CVSS 4.0 9.3; vendor advisory states 9.8), while independent assessment rates it high with high attack complexity because the bypass exists only during the resource-exhaustion window; no public exploit code identified at time of analysis, no KEV listing, and CWE-636 (Failing Open) is the root class.

IBM Verify Identity Access (and its predecessor Security Verify Access) contains an improper authorization flaw that lets an administrator with limited entitlements execute additional commands beyond their granted privileges by supplying specially crafted input to the product's administrative functionality. The flaw carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), reflecting high confidentiality, integrity and availability impact but requiring an existing privileged account to reach. No public exploit code or CISA KEV entry was identified at time of analysis, and IBM has published a vendor fix via its support advisory.

Improper authorization in Atlassian Jira Service Management Data Center 11.3.0 through 11.3.10 lets an authenticated, low-privileged attacker reach functionality and data they should not be able to access, with the vendor scoring it 7.1 in CVSS 4.0 (AV:N/AC:L/PR:L/UI:N/VI:H). Atlassian states the flaw was discovered through its own penetration-testing program and that the impact could extend from exposure of sensitive resources to arbitrary code execution, though the published CVSS 4.0 vector only credits a high integrity impact and rates confidentiality and availability as none. No CISA KEV listing, EPSS score, or public exploit code was provided in the source data, so at time of analysis this should be treated as a confirmed but not yet observed-in-the-wild authorization bypass; patched versions (11.3.11 and later) are already available.

An improper authorization flaw in Atlassian Confluence Data Center lets an authenticated, low-privileged user reach resources and functionality they should not be able to access, resulting in high confidentiality impact against the affected instance. The defect was introduced across a broad set of release trains — 7.4.0, 7.13.0, 8.5.0, 8.9.0, 9.0.1, 9.1.0, 9.2.0, 9.3.1, 9.4.0, 9.5.1, 10.0.2, 10.1.0 and 10.2.0 — meaning most currently maintained Data Center deployments built on those lines are exposed until upgraded. Atlassian rates the issue 7.1 (CVSS 4.0, AV:N/AC:L/PR:L/UI:N/VC:H) and has shipped fixes in 9.2.24 and 10.2.17; there is no evidence of public exploit code or confirmed active exploitation at time of analysis.

Let me analyze this CVE and produce the JSON. CVE-2026-63443: Coder workspace agent API insecure redirect handling. Affected: Coder (coder/coder) versions < 2.29.19, < 2.32.9, < 2.33.10, < 2.34.4. CVSS 8.3, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. CWE-863 (Incorrect Authorization). Attacker: authenticated user with running workspace and control over modified workspace agent; knows victim agent UUID → derives tailnet IP. Redirects control-plane requests to victim agent. File read/write as victim, and process API command execution. Tags: Authentication Bypass, Hashicorp, Coder. Hashicorp tag is mislabeled — Coder is not HashiCorp (though it uses Terraform, which is HashiCorp). Actually description mentions Terraform "allows organizations to provision remote development environments via Terraform". The tag "Hashicorp" is arguably wrong — Coder Inc. is the vendor. Hmm, but they do build on Terraform. I'd flag "Hashicorp" as wrong_vendor with suggested "coder". Confidence high? The CPE is coder:coder. Yes, flag it. Also "Authentication Bypass" tag — this is more of a broken access control / cross-tenant redirection, not really auth bypass. But I'm less confident; the guidance says only flag mislabeled tags I can verify. "Authentication Bypass" is arguably a mislabel since exploitation requires authenticated user (PR:L). Hmm. I could flag it as mislabeled_tag with suggested "authorization bypass" or something. But suggesting a tag slug... maybe "broken-access-control". It's borderline. I'll consider including it with medium confidence. Actually the instructions say only emit when highly confident and verifiable. The tag "Authentication Bypass" conflicts with PR:L authenticated. I think it's reasonably confident this is not an authentication bypass — it's an authorization/redirect flaw. I'll include it with medium confidence. Hmm, risk of noise. Let me include both: wrong_vendor for "Hashicorp" (high) and mislabeled_tag for "Authentication Bypass" (medium). Maybe also miss

Stored cross-site scripting in Concrete CMS lets any user holding page-editing permissions — for example Add Block combined with Edit Contents on a single page — plant a crafted external link value in Feature, Feature Link, Hero Image, or Image blocks that breaks out of the link markup and injects JavaScript. Because the payload is persisted and rendered without output escaping, the script executes in the browser session of every user who later views, previews, or edits that page, enabling session hijacking and privilege escalation up to full administrative takeover. The vendor scored this 8.5 (CVSS v4.0, PR:H/UI:P); no public exploit code or CISA KEV entry was provided at time of analysis, so exploitation is currently a realistic internal-threat and low-privileged-editor risk rather than a confirmed internet-wide campaign.

Unauthenticated user enumeration in Concrete CMS 9.0.0 through 9.5.2 allows any anonymous visitor to dump the complete backend account list — including internal user IDs, usernames and email addresses of every administrator and the super-administrator (user ID 1) — by sending an empty search to the /ccm/system/user/autocomplete endpoint and paginating the results. The endpoint enforces only a CSRF-style token that is bound to the selector's display options rather than to caller identity, and that token is handed out to anonymous visitors, so there is no authentication or privilege barrier to clear. No password hashes or session material leak, but the disclosed email and account inventory is a ready-made target list for credential stuffing, phishing and password-spray campaigns against named admins; no public exploit code and no CISA KEV entry are present in the supplied intelligence.

Any authenticated user of a Payload CMS instance running @jhb.software/payload-cloudinary-plugin (0.3.0 through 0.3.x, fixed in 0.4.0) can obtain a cryptographically valid Cloudinary HMAC-SHA1 upload signature for parameters of their choosing, because the client-upload signing endpoint POST /api/cloudinary-generate-signature forwards attacker-controlled 'paramsToSign' straight to cloudinary.utils.api_sign_request() with no key allowlist, folder policy, or timestamp check. With that signature plus the intentionally client-visible Cloudinary API key, an attacker can overwrite existing assets, flip upload visibility with type=private, register notification_url callbacks to attacker-chosen hosts, force cache invalidation, and write files outside the intended upload folder. The issue is only reachable when the plugin's clientUploads option is enabled, and no public exploit code or active-exploitation reporting was present in the supplied intelligence.

Authentication bypass in BookStack social login (all versions before 26.05.5) allows unauthenticated attackers to sign in as arbitrary users, enabling full account takeover of both regular accounts and administrators. The flaw is a provider-confusion bug in SocialAuthService::handleLoginCallback, which retrieves linked-account records by driver_id while ignoring the driver column, so an attacker who authenticates at one enabled social provider using a user ID that collides with a victim's driver_id under a different provider is accepted without credential verification. No public exploit identified at time of analysis (CISA SSVC exploitation: none; no KEV listing), and successful exploitation requires two enabled social providers sharing an overlapping driver_id namespace plus attacker control of a matching provider account, which is why vendor scoring lands at CVSS 9.1 while our independent vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) caps the attack at high complexity.

Authorization bypass flaws in the 'Design Scuole Italia' WordPress theme (design-scuole-wordpress-theme, versions up to and including 2.17.3) let an unauthenticated remote attacker reach content and data that should require a logged-in, authorized user. The faulty routines are the dsi_pdf_generator and dsi_csv_generator functions, and an unauthenticated RSS feed at /circolare/feed/ gives an additional, easily scriptable path to the same restricted 'Circolare' records and registered-user information. With a CVSS 4.0 base score of 8.7, no privileges or user interaction required, and high confidentiality impact, this is a straightforward data-exposure bug in a theme deployed mainly on Italian school websites; no public exploit code or CISA KEV entry was identified at time of analysis.

Vikunja instances before 2.6.0 expose CalDAV BasicAuth endpoints (/dav, /.well-known, and /feeds) that are not covered by the application's anti-brute-force controls, letting a remote unauthenticated attacker send an unlimited number of credential-guessing requests. Successful guessing against password-only accounts yields full read access to the victim's tasks, projects, and feeds data. The vendor has released 2.6.0 as the fix; no public exploit code or active exploitation has been confirmed in the supplied intelligence.

Unauthenticated remote attackers can bypass the RDSTLS-disabling policy on FreeRDP servers 3.0.0 through 3.30.0 by sending incompatible protocol requests that produce a negotiation failure, then completing a TLS handshake and entering RDSTLS anyway, defeating the intended pre-authentication transport restriction. The vendor CVSS 4.0 base score is 9.2, but our independent CVSS 3.1 assessment is AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, reflecting a policy bypass with limited confidentiality and integrity impact rather than direct code execution; no public exploit was identified at time of analysis. Only network-reachable FreeRDP server-mode deployments with RDSTLS administratively disabled are affected, while client-side FreeRDP deployments are not impacted.

Broken object-level authorization in Flowise's openai-realtime endpoints lets any authenticated user read tool definitions and execute tools belonging to ChatFlows in other workspaces by supplying an unscoped chatflowid, with both GET and POST requests affected. The flaw is fixed in Flowise 3.1.4 and affects all earlier releases; it is tracked as CWE-639 (authorization bypass through user-controlled key). No public exploit code or CISA KEV entry was identified at time of analysis, and EPSS data was not supplied with this record, so risk should be judged from the authenticated-but-cross-tenant access model rather than from observed exploitation.

Cross-tenant authorization bypass in Flowise Enterprise endpoints (all versions before 3.1.4) allows an authenticated Enterprise user to operate on resources owned by other organizations — deleting arbitrary workspaces, inviting themselves into other tenants, modifying cross-organization roles, and reading or abusing stored SSO secrets. The root cause is CWE-862 (missing authorization): affected endpoints act on caller-supplied resource identifiers without verifying tenant ownership. Rated CVSS 7.6 (CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L), reachable over the network but requiring low-privileged Enterprise access; a vendor patch is available in 3.1.4, and no public exploit has been identified at time of analysis.

Session fixation in Dell SmartFabric OS10 Software versions prior to 10.6.1.3 allows remote, unauthenticated attackers to plant or predict a management session identifier and subsequently hijack that session once a legitimate administrator logs in, resulting in session theft with the full privileges of the compromised account. Dell's published CVSS 3.1 vector scores this 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but that score overstates the issue on two counts: successful exploitation hinges on a victim authenticating into the attacker-controlled session (effectively a user-interaction requirement, UI:R), and the real-world impact is bounded by the privileges of the hijacked account, making confidentiality and integrity exposure meaningful but not unconditional. There is no public exploit identified at time of analysis - CISA SSVC records no observed exploitation and no proof-of-concept code is referenced - and the attacker can only realize impact through a victim-logon step, so the practical risk is lower than the raw 9.8 suggests while still warranting prompt patching of internet- or management-plane-reachable deployments.

An authentication bypass in OpenBMC's phosphor-net-ipmid IPMI stack lets a network attacker with no credentials complete IPMI 2.0 RAKP session authentication and obtain full BMC control. A crafted RAKP Message 1 forces the handler to return before the authentication object's constructor defaults are overwritten, so the service accepts a RAKP Message 3 whose HMAC is keyed with the hard-coded 20-byte 'userKey' derived from the string '0penBmc' combined with an often-predictable 'bmcRandomNum'. The flaw affects downstream vendors that ship phosphor-net-ipmid as their IPMI implementation, including NVIDIA and H3C, and runZero published a public advisory; no CISA KEV entry or EPSS score was supplied, and no patched version was identified in the provided data.

Privilege escalation in OpenBMC's phosphor-net-ipmid IPMI stack allows an attacker who already holds a valid low-privileged IPMI session to redirect that session's authorization context to a different, higher-privileged account while the original integrity and encryption keys stay in place, so no re-authentication ever occurs. Downstream vendors that package phosphor-net-ipmid — NVIDIA and H3C among them — inherit the flaw in their BMC firmware. Rated CVSS 8.8 with high confidentiality, integrity and availability impact; no public exploit code identified at time of analysis, and the issue is not listed in CISA KEV.

Cross-organization user administration takeover in Casdoor through 4.4.0 allows any holder of a single application's clientId and clientSecret to act on user accounts across all organizations. The flaw is an authorization bypass in the /api/mcp endpoint that exposes password salts, email addresses, and account creation/modification/deletion capabilities. Public exploit documentation exists, but no active exploitation status or EPSS data was provided.

Unauthenticated information disclosure in Dromara lamp-cloud through 5.10.0 stems from an overly broad anonymous-access whitelist pattern (/*/anno/**) that exposes the /defGenProject/anno/getProperties endpoint. Any remote attacker who can reach the service via HTTP can POST to that path and receive the server's complete JVM system property map, leaking classpath entries, filesystem paths, OS build details, and startup secrets injected as properties. Exploit code is publicly available (a writeup and proof-of-concept are linked from the CVE references and VulnCheck advisory), and the flaw has not been listed in CISA KEV, so it is a high-value reconnaissance and credential-harvesting primitive rather than a confirmed mass-exploitation event.

Unauthenticated credential takeover in pig-mesh Pig before 4.1.0 allows any remote attacker who can reach the /register/password endpoint to overwrite the password of an arbitrary account, including the built-in 'admin' account, and thereby obtain full administrative control of the platform. The flaw is an authentication bypass: the endpoint's password-reset logic calls checkPassword() but discards the boolean result, so the submitted 'current password' is never actually validated. Publicly available exploit code exists (a proof-of-concept write-up and the upstream issue are linked), and the vendor has released version 4.1.0 as the fix; there is no indication of confirmed exploitation in CISA KEV at the time of analysis, but the combination of unauthenticated remote exploitation, high impact (CVSS 4.0 base 9.3; independently assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and public exploit code makes rapid patching warranted.

Semaphore UI through 2.19.12 fails to enforce project-level resource permissions on GET and HEAD requests in its GetMustCanMiddleware, letting any authenticated user holding only the low-privileged guest or task_runner role read every project's environment records. Those environment records store plaintext secrets, credentials, and passwords used to reach managed infrastructure, so a read-only account can effectively harvest the keys to the entire estate. Publicly available exploit code exists (tracked by VulnCheck, issue #4150), the flaw is rated 7.1 with a network attack vector and low privileges required, and no CISA KEV listing has been observed at time of analysis.

Missing authorization on pgweb's POST /api/connect endpoint through version 0.17.0 lets attackers bypass the connect-backend resource-to-database mapping by submitting a custom session identifier and arbitrary connection URL, granting access to databases and internal services the operator never intended to expose. The flaw is CWE-862 (missing authorization) and carries a CVSS 4.0 base score of 8.4 (AV:N/AC:L/PR:L/UI:N, high confidentiality impact on both the vulnerable system and subsequent systems), reflecting that a successful attacker can read arbitrary backend data while the pgweb host is used as a pivot. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so exploitation is currently assessed as opportunistic rather than confirmed active.

Authentication bypass in praisonai-platform before 0.1.6 lets any remote unauthenticated attacker mint a valid HS256 JSON Web Token and impersonate arbitrary users against protected API routes. The flaw is a hardcoded fallback signing secret ('dev-secret-change-me') combined with a production guard that never fires when the operator leaves both PLATFORM_JWT_SECRET and PLATFORM_ENV unset - the common mis-deploy - so the platform silently starts signing tokens with a publicly known literal drawn straight from the source code. CVSS 3.1 scores this 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and EPSS is 0.51% (42nd percentile); there is no CISA KEV listing and no public exploit identified at time of analysis, though exploitation requires nothing more than a forged token and no authentication whatsoever.

Unauthenticated authentication bypass in praisonai-platform prior to 0.1.6 (and PraisonAI before 4.6.51) allows a remote attacker to forge HS256 session JWTs using the publicly known default signing key 'dev-secret-change-me' and be accepted as any identity the attacker names in the token's sub claim, including a workspace owner. The vulnerable state is the shipped default: the documented startup command sets neither PLATFORM_JWT_SECRET (so the hardcoded fallback is used) nor PLATFORM_ENV (which stays at 'dev', leaving the startup and token-issuance guards default-open). CVSS 3.1 scores this 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), consistent with an unauthenticated full-compromise primitive; EPSS is low at 0.53% (43rd percentile), no public exploit code was identified at time of analysis, and there is no CISA KEV listing, although the flaw is trivially exploitable against default deployments and the only practical constraint is that workspace-owner takeover requires knowing the target owner's user/sub identifier.

Unauthenticated access to the AgentOS HTTP server shipped in the npm `praisonai` package (versions 1.6.0 through 1.7.1) allows any remote caller who can reach the service to read configured agent names, roles and the first 100 characters of each agent's instructions via GET /api/agents, and to invoke a chosen agent through POST /api/chat, potentially reaching that agent's tools, memory, external APIs, credentials and workflow state. The default configuration binds to 0.0.0.0 with corsOrigins set to ['*'] and registers both routes without any authentication or authorization middleware (CWE-306), so the missing-authentication weakness applies unauthenticated over the network (CVSS 3.1 PR:N); version 1.7.2 is the vendor-released fix. No public exploit code has been identified at time of analysis, EPSS is low at 0.56% (45th percentile) and the issue is not in CISA KEV, but CISA SSVC rates it automatable with total technical impact and the exposure depends entirely on whether an operator has left AgentOS reachable on a routable interface.

PraisonAI's TypeScript MCP server (npm package `praisonai`, versions 1.5.0 through 1.7.1) exposes an HTTP JSON-RPC transport that performs no authentication or authorization, so any network client that can reach the listening port can call tools/call, resources/read, or prompts/get and trigger registered handlers with the server process's credentials and privileges. The server's startHttp() binds the unspecified address (all interfaces) with no host restriction and ignores the Authorization header entirely; the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8) confirms this is unauthenticated and remotely reachable, though exploitation requires the operator to have enabled the HTTP transport and made the port network-reachable. Publicly available exploit code exists (a public gist), but there is no evidence of confirmed active exploitation, and the EPSS score is low at 0.64% (49th percentile); the vendor-released fix is version 1.7.2.

Let me synthesize. Key facts: - CVE-2026-57134, PraisonAI (npm package "praisonai", TypeScript MCP security helper). - MCPSecurity.evaluatePolicy() only validates credentials for api-key/bearer; basic/oauth accept any non-empty Authorization header, skipping validate() callback, returning authenticated: true. - Affected: npm praisonai >= 1.5.1, <= 1.7.1; fixed in 1.7.2. CPE cpe:2.3:a:mervinpraison:praisonai:*:*:*:*:*:*:*:* - CVSS 8.2 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N. But logically, exploitation requires the deployment to use basic or oauth auth policy — that's a configuration prerequisite. Hmm. CVSS PR:N given. My assessed vector: I'd argue PR:N is defensible from the attacker's perspective (attacker sends an arbitrary Authorization header without valid credentials). But the configuration requirement: the target must use basic/oauth policy. AV:N is fine. AC:L? Arguably AC:H because it requires non-default config (basic/oauth policy configured). Let me think: the guidance says choose PR honestly — if exploitation requires control over configuration files, admin access, or authentication, use PR:H or PR:L. Here the attacker doesn't need config access; they need the target to have configured basic or oauth. That's a configuration precondition, not attacker privilege. I'd keep PR:N and use AC:H? Hmm. Many would keep AC:L. Actually the exploit is trivially automatable once the target uses basic/oauth. I'll go AC:L, PR:N, but note the pre-condition. Hmm, but the rubric's example: "Requires write access to the httpd configuration, so PR:H and AC:H". That's different. Here attacker just sends header. I'll use AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N — matching but I should express independent judgment. Maybe I could argue I:L and A:N as given. Let me consider C:H — access to MCP tools and resources protected by policies → confidentiality high, integrity low. That's reasonable. I'll go with AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N — but then it's a copy. The instruction says "NOT

Unauthenticated MCP tool invocation in PraisonAI (praisonaiagents 0.6.0–1.6.58 and praisonai 3.10.0–4.6.58) lets a malicious website use DNS rebinding to reach a local or internal ToolsMCPServer SSE endpoint on /sse and /messages/, enumerate registered tools, and invoke them with the server user's privileges. The legacy SSE wrapper performs no Host, Origin, or authentication enforcement, while the newer Streamable HTTP transport rejects the same hostile Origin with HTTP 403, isolating the flaw to the legacy SSE path. An initial remediation ships in praisonaiagents

MISP through 2.5.45 fails to enforce authorization checks when collection elements are created, allowing an authenticated user to persist a bare UUID referencing an Event or Galaxy Cluster they are not permitted to read. The collection view later resolves that UUID back into the underlying object, so collections become a handle on another organisation's private data — the patch notes this already caused org-only events to be disclosed in the beta collection view. Exploitation requires a valid MISP account and knowledge of the target UUID; no public exploit code or CISA KEV listing was identified at time of analysis, though the CVSS 4.0 vector (PR:L, VC:H) and EPSS-adjacent signals mark it as a meaningful confidentiality risk for shared threat-intel instances.

An authorization bypass in MISP through version 2.5.45 lets an authenticated user who can edit events assign an arbitrary sharing_group_id they are not authorized to use, because the authorization check only ran when the request explicitly supplied distribution = 4. If the caller omits the distribution field, MISP's field-recovery logic restores the event's stored distribution (4, for sharing-group events) and persists the unauthorized sharing group ID, silently re-scoping who can see that event and its threat-intelligence content. No public exploit code or active exploitation has been identified at time of analysis, but exploitation is a single crafted edit request, so the integrity impact (VI:H, CVSS 4.0 base 7.1) is significant for multi-tenant or community-sharing MISP instances.

Incorrect authorization validation in Octopus Server permits authenticated users holding certain scoped permission sets to execute arbitrary scripts on deployment workers, including the built-in worker that runs directly within the Octopus Server process. The flaw bypasses the permission check that should gate script execution, allowing a user to operate outside their authorized scope without possessing the required authorisation. No public exploit has been identified and the CVE is not in CISA KEV, but the low authentication barrier - any user with some scoped permissions - makes this a meaningful privilege-escalation risk in CI/CD environments where Octopus Server routinely holds deployment credentials and infrastructure access.

Trust-boundary spoofing in the proxy-addr Node.js module (versions 1.1.0 through 2.0.7), the library that backs Express req.ip and req.ips, lets unauthenticated clients forge their apparent source address. When an operator declares a trusted-proxy subnet in IPv4-mapped IPv6 notation with an IPv4-sized prefix (e.g. ::ffff:10.0.0.0/8 rather than the correct /104), proxy-addr silently accepts it but trusts every IPv4 address on the internet, so the direct socket peer becomes trusted at hop 0 and any client can set an arbitrary X-Forwarded-For header. This is a fail-open regression introduced in 1.1.0, fixed in 2.0.8; no public exploit identified at time of analysis, and it is not in CISA KEV.

Insufficient session expiration in bizwell xClick groupware allows authentication bypass through replay of session tokens that should have been invalidated after logout or timeout. Affecting versions R2, R3, and R3.1, the flaw enables an attacker who has obtained a victim's session token to continue using it with full account-level access even after the legitimate session should have ended, carrying high confidentiality, integrity, and availability impact per the CVSS 4.0 score of 8.7. No public exploit code has been identified at time of analysis, and the vulnerability does not appear in the CISA Known Exploited Vulnerabilities catalog.

Authorization bypass in IceHRM before 36.0.0 lets any authenticated employee read coworkers' HR records by substituting an arbitrary employee ID in seven REST sub-resource endpoints covering skills, education, certifications, languages, leave, attendance and status. CVSS 4.0 scores the flaw 7.1 (AV:N/AC:L/PR:L/UI:N, VC:H only), reflecting a low-effort, easily automated disclosure of sensitive personnel data rather than code execution. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV; a vendor fix is available in release v36.0.0.

Scheduled-job management functionality in 1024-lab SmartAdmin v3.30.0 is exposed without method-level permission checks, so any user who already holds a valid low-privileged account can reach administrator-only endpoints in AdminSmartJobController. Successful exploitation yields high confidentiality and integrity impact — job definitions and their parameters can be read, created, modified, or deleted — while availability is not directly affected per the CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, base 8.1). There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score was supplied, so current risk is driven by exposure of the application to authenticated non-admin users rather than by observed mass exploitation.

Remote code execution in RuoYi-Vue-Plus 6.0.0 lets an authenticated low-privileged user run arbitrary Java code on the server through the workflow task-completion endpoint POST /workflow/task/completeTask, which flows through FlwTaskController.java into FlwTaskServiceImpl.completeTask, CompleteExecuteComponent.process and the Warm-Flow TaskService.skip path. The CVSS 3.1 base score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting network reachability and complete confidentiality, integrity and availability impact, but it requires a valid authenticated session rather than being pre-auth. No public exploit code or CISA KEV entry was identified from the supplied intelligence, and no EPSS score was provided.

Unauthenticated retrieval of Stripe Checkout Session objects in the MarcosCamara01 Ecommerce Template (before commit 91e273c) exposes buyer personally identifiable information to anyone holding a session id. The GET handler at /api/stripe/checkout_sessions calls stripe.checkout.sessions.retrieve() and returns the full object — buyer name, email, phone, billing address, amount paid and internal userId — without ever calling auth.api.getSession() or verifying that the session belongs to the caller, even though sibling endpoints such as POST /api/stripe/payment already enforced authentication. Exploitation is not confirmed in the wild and no public exploit code was identified, but the session_id is written into the buyer's own success_url (/result?session_id={CHECKOUT_SESSION_ID}), so it leaks through Referer headers, analytics, access logs and shared-machine browser history, making the flaw practically reachable rather than purely theoretical.

Improper access control in IBM Sterling File Gateway (6.2.0.0 through 6.2.0.6_1, 6.2.1.0-6.2.1.2, and 6.2.2.0-6.2.2.1) lets a remote, unauthenticated attacker reach file-transfer data they should not be able to see. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H) describes a trivially reachable, no-credentials-required read of sensitive information with no integrity or availability impact. No public exploit code or CISA KEV entry was present in the supplied intelligence at the time of analysis, and IBM has published a vendor fix.