Authentication Bypass
Monthly
Broken access control in springboot-project v1.0.0 lets remote unauthenticated attackers reach every seller-management interface through a flaw in the SellerAuthorizeAspect authorization component. Attackers can enumerate all products and orders, toggle products on/off sale, finish or cancel orders, and modify categories with no credentials. No public exploit identified at time of analysis beyond the reporter's write-up; EPSS is low at 0.18% (7th percentile).
Unauthenticated remote attackers can log into sso-master v1.0.0 without supplying a password by sending a single crafted POST request to the CAS /cas/login endpoint, gaining full application access with high confidentiality and integrity impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N; vendor-published base 9.8). No valid credentials, user interaction, or special client configuration are required, and the assessment notes no availability impact. Despite the critical score, the practical risk is limited by deployment scarcity - this is a niche v1.0.0 open-source SSO project with no known enterprise footprint - and the low EPSS of 0.14% (4th percentile) reinforces that exposure is narrow; there is no CISA KEV listing and no confirmed public exploit code flagged in the supplied intelligence, although a public GitHub write-up demonstrates the affected endpoint. The signals conflict sharply: a maximum-severity authentication bypass paired with near-floor exploit-prediction and no observed exploitation.
Missing authentication in Knowns (knowns-dev/knowns) before 0.30.0 exposes the management API on all network interfaces (0.0.0.0) by default with no password set on fresh installs, letting anyone with network reachability drive the server. Attackers can call the unauthenticated /api/tunnel/start endpoint to spin up a public tunnel that republishes the entire management API at an internet-reachable address, escalating a LAN-only exposure into full public exposure. Reported by VulnCheck and fixed in v0.30.0; publicly available exploit code exists in the sense that the vulnerable endpoints and fix are documented, but no active exploitation is confirmed (not in CISA KEV).
Improper Certificate Validation (CWE-295) in Dell Secure Connect Gateway (SCG) 5.0 allows an unauthenticated attacker positioned on the same network segment to intercept or manipulate TLS-protected communications, leading to unauthorized access to sensitive data or remote-support sessions. Both the Appliance variant (versions prior to 5.36.00.16) and the Application variant (versions prior to 5.36.00.00) are affected. The CVSS AV:A vector confirms this is not a direct internet exploit - the attacker must be adjacent to the network segment hosting the SCG deployment. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Local code execution on Remote Development hosts is possible in JetBrains IntelliJ IDEA versions before 2026.2.2 due to the IJent gRPC server running without TLS encryption or any authentication mechanism. The IJent agent, deployed on remote hosts when the Remote Development feature is in use, accepts connections from any local process without requiring credentials, enabling arbitrary command execution under the agent's security context. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Privilege escalation to superuser in JetBrains Hub before 2026.2.52442 allows an unauthenticated remote attacker to register a trusted service and thereby obtain full administrative (superuser) control over the identity-management server. Because Hub is the single sign-on and authorization backbone for JetBrains tooling (YouTrack, TeamCity, Upsource), compromise cascades to every application relying on it for authentication. No public exploit has been identified at time of analysis, and the CVE is not listed in CISA KEV.
Unauthenticated account takeover in JetBrains YouTrack's Helpdesk feature allows a remote attacker to hijack existing accounts by asserting a victim's email address without proving ownership of it. All YouTrack builds before 2025.3.161254 and 2026.1.14042 are affected. Because the flaw is a trust failure in how Helpdesk associates a self-provided email with an account, exploitation requires no credentials, no user interaction, and works against default configurations where Helpdesk is enabled. No public exploit identified at time of analysis.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 exposes both Appliance and Application variants to protection mechanism bypass by unauthenticated remote attackers. The flaw (CWE-295) allows an adversary in a network-interception position to present an invalid or attacker-controlled TLS certificate that the SCG accepts without proper verification, potentially enabling interception or manipulation of communications between the gateway and backend or managed systems. Patch availability is confirmed via Dell advisory DSA-2026-382; no public exploit or CISA KEV listing is present at time of analysis.
Unauthorized remote access to Dell Secure Connect Gateway (SCG) 5.0 is possible through a logic flaw rooted in CWE-480 (Use of Incorrect Operator), affecting both the Appliance variant (prior to 5.36.00.16) and the Application variant (prior to 5.36.00.00). The incorrect operator in a security-relevant conditional-likely an authentication or authorization check-produces a logic outcome that permits access without valid credentials, consistent with the CVSS PR:N vector and the 'Authentication Bypass' classification. Real-world impact spans limited confidentiality, integrity, and availability loss per the CVSS L/L/L impact ratings; no public exploit code or CISA KEV entry has been identified at time of analysis.
Authentication bypass in 389 Directory Server (shipped as Red Hat Directory Server 11-13 and within RHEL 6-10) lets remote unauthenticated attackers assume Directory Manager authority without valid credentials. A stale SASL auxiliary identity left over from a failed SASL PLAIN bind is incorrectly installed onto the connection when a later, unrelated bind (e.g. SASL ANONYMOUS) succeeds on the same connection. No public exploit was identified at time of analysis, and the flaw is not listed in CISA KEV, but the trivially reproducible bind sequence makes weaponization straightforward.
Improper TLS certificate validation in Dell Secure Connect Gateway 5.0 allows an unauthenticated remote attacker occupying a man-in-the-middle network position to intercept and tamper with encrypted SCG communications, leading to unauthorized access. Both the physical Appliance variant (fixed in 5.36.00.16) and the virtual Application variant (fixed in 5.36.00.00) are affected across all 5.0.x releases preceding those thresholds, per Dell advisory DSA-2026-382. No public exploit code or active exploitation has been identified at time of analysis.
Missing authentication on critical API functions in Dell Secure Connect Gateway (SCG) 5.0 exposes privileged operations to remote unauthenticated attackers, enabling unauthorized access that yields high integrity impact and limited confidentiality exposure. Both deployment forms - the virtual Appliance (prior to 5.36.00.16) and the Application (prior to 5.36.00.00) - are affected. Dell has released patches via advisory DSA-2026-382; no public exploit or CISA KEV listing exists at time of analysis, but the attack path (AV:N/AC:L/PR:N/UI:N) requires minimal attacker capability.
Unauthenticated remote exploitation of Dell Secure Connect Gateway (SCG) 5.0 - both the Appliance variant (prior to 5.36.00.16) and Application variant (prior to 5.36.00.00) - exposes a critical function with no authentication gate, allowing a network-adjacent or internet-facing attacker to trigger high-availability-impact operations without any credentials. Dell's advisory DSA-2026-382 classifies this under CWE-306 (Missing Authentication for Critical Function), indicating the affected endpoint simply lacks access control rather than having a bypassable one. No public exploit code or CISA KEV listing is confirmed at time of analysis, though the fully unauthenticated network vector with low complexity represents a credible operational risk for any exposed SCG deployment.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 allows remote unauthenticated attackers to bypass TLS protection mechanisms, enabling man-in-the-middle interception or modification of communications to and from the gateway. Both the Appliance form factor (versions prior to 5.36.00.16) and Application form factor (versions prior to 5.36.00.00) are confirmed affected by Dell advisory DSA-2026-382. No public exploit code exists and EPSS scoring of 0.14% (4th percentile) reflects very low current exploitation probability, consistent with SSVC's 'none' exploitation status.
Unauthorized remote access to Dell Secure Connect Gateway (SCG) 5.0 is possible because the product fails to properly validate TLS certificates (CWE-295), affecting the Appliance edition before 5.36.00.16 and the Application edition before 5.36.00.00. An unauthenticated network attacker able to intercept or interpose on connections can defeat the trust chain and gain access to protected resources or data. A vendor patch is available (DSA-2026-382); no public exploit identified at time of analysis and EPSS is low (0.15%).
Unauthenticated integrity compromise in 389 Directory Server (shipped as Red Hat Directory Server 11/12/13 and bundled in RHEL 6-10) allows anonymous LDAP clients to bypass SELFDN-based access control checks. The SELFDN ACI bind-rule evaluator incorrectly equates an anonymous client's empty bind DN with an empty stored attribute value in a target directory entry, satisfying an ACI that was intended to permit only a matching authenticated identity. Exploitation enables anonymous directory modifications - including adding or altering entries - that SELFDN ACIs were designed to restrict to specific authenticated users. No public exploit has been identified at time of analysis.
Authentication bypass in the LibreNMS REST API (all versions before 26.8.0) lets unauthenticated remote attackers reach protected endpoints by submitting a small integer (0-9) in place of a string API token, abusing MySQL loose type coercion so the integer matches a stored token hash. Successful bypass exposes device credentials and administrative functionality, and can be chained to remote code execution through alert templates. Reported by VulnCheck; no public exploit is identified at time of analysis, though the type-confusion technique is fully described in the advisory.
Dell Secure Connect Gateway (SCG) 5.0 exposes a critical management function without any authentication requirement (CWE-306), enabling an unauthenticated remote attacker to achieve full confidentiality, integrity, and availability compromise against affected deployments. Both the Appliance variant (versions prior to 5.36.00.16) and the Application variant (versions prior to 5.36.00.00) are confirmed vulnerable per Dell advisory DSA-2026-382 and EUVD-2026-72375. No public exploit has been identified at time of analysis; Dell has released patches for both deployment forms.
Hard-coded credentials embedded in Dell Secure Connect Gateway (SCG) 5.0 expose both the Appliance and Application deployments to unauthenticated remote compromise. A network-accessible attacker who discovers or obtains the static credentials can authenticate without any supplied privileges and gain unauthorized access with high confidentiality and integrity impact. No public exploit or active CISA KEV listing has been identified at time of analysis; Dell has confirmed the vulnerability and released fixed versions via advisory DSA-2026-382.
Account takeover in Bahçelievler Municipality's BiHayat App (versions 2.1.7 through build 07092026) is possible because the authentication flow imposes no limit on repeated login attempts, letting remote attackers brute-force credentials or bypass authentication controls entirely. TR-CERT reported the flaw and the vendor did not respond to disclosure. There is no public exploit identified at time of analysis and it is not in CISA KEV.
Remote command execution in Dell Secure Connect Gateway 5.0 (Appliance versions before 5.36.00.16 and Application versions before 5.36.00.00) lets a remote, unauthenticated attacker run commands on the target by sending a specially crafted request that bypasses intended authorization checks. Dell has released fixed versions and the flaw is rated critical (CVSS 9.4). No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated privilege escalation in FreeIPA (Red Hat Identity Management) allows a remote attacker to gain genuine administrators-group membership. The self-managed OTP token ACI does not require authentication and fails to restrict which attributes may be added alongside a token entry; chained with a separately-tracked directory-server ACI evaluation flaw, an unauthenticated LDAP client can create an attacker-controlled Kerberos principal and place it in the administrators group. Assigned CVSS 9.8 (CWE-306, Missing Authentication); no public exploit identified at time of analysis and it is not listed in CISA KEV.
Authentication bypass in the WebGUI of NEC's UNIVERGE IX-R/IX-V series network routers allows remote attackers to tamper with WebGUI messages and execute arbitrary CLI commands on the device without valid credentials. Because the affected management interface can be reached over the internet, an unauthenticated attacker can gain administrative-level command execution, effectively compromising the router's configuration and traffic-handling. No public exploit has been identified at time of analysis, but the CVSS 4.0 base score of 9.3 reflects the low complexity and high impact.
Tunneled EAP authentication in strongSwan before 6.1.0 can be bypassed when the IKEv2 responder fails to properly enforce inner EAP method authentication details, enabling a network attacker with a low-privilege outer-tunnel identity to obtain an authorized VPN session without completing the inner credential exchange. The flaw (CWE-863, Incorrect Authorization) is limited to deployments using tunneled EAP methods such as EAP-TTLS or EAP-PEAP; certificate-only or non-tunneled EAP configurations are not affected. Vendor-released patch strongSwan 6.1.0 is available; no public exploit identified at time of analysis.
SAML authentication bypass in the Perl module MojoX::Authentication before 0.006 lets a remote unauthenticated attacker impersonate any user by forging a SAML response. The module's parse_assertion routine constructs a Net::SAML2::Binding::POST object without any trust anchor (no cacert, cert_text, or anchors), so the signature on an unencrypted assertion is validated against the certificate embedded in the response itself rather than the trusted IdP signing certificate. No public exploit has been identified at time of analysis, and EPSS is low (0.11%), but the flaw is a complete pre-authentication account-takeover primitive.
Unauthenticated account takeover in the Frontend Admin by DynamiApps WordPress plugin (all versions through 3.29.12) lets remote attackers overwrite any user's email address - including an administrator's - and then hijack the account via WordPress's built-in password-reset flow. The flaw stems from a missing capability check in pre_update_value combined with an authorization gate that is silently bypassed when a non-numeric post identifier (e.g. 'user_1') is supplied. Reported by Wordfence; no public exploit code or CISA KEV listing was identified at time of analysis, but the trivial, unauthenticated nature makes this a high-priority patch.
Authentication bypass in HivePress Authentication plugin for WordPress (≤1.1.4) allows an unauthenticated network attacker to log in as any WordPress user - including administrators - whose account email is linked to a Facebook account. The plugin's Facebook OAuth handler forwards the caller-supplied access_token directly to the Facebook Graph API and blindly trusts the returned email and user ID, performing no /debug_token audience validation and no comparison of the token's app_id against the configured hp_facebook_app_id. Exploitation requires the attacker to first acquire a valid Facebook access token associated with the victim's account, which is the primary complexity barrier - but once obtained, the attack yields full account takeover with no WordPress credentials required. No public exploit or CISA KEV listing has been identified at the time of analysis.
Full account takeover in the MemberDash WordPress membership plugin (versions up to and including 1.8.5) lets unauthenticated remote attackers reset the password of any user - including administrators - by supplying an arbitrary target user ID via the 'id' parameter during registration. The victim receives no notification, so takeover is silent. Reported by Wordfence with a critical 9.8 CVSS; no public exploit is identified at time of analysis, though the trivially scriptable request pattern makes weaponization straightforward.
Remote unauthenticated exploitation of MikroTik RouterOS's Bandwidth Test (btest) service allows two distinct attacks: kernel memory disclosure and kernel crash/restart. The btest server accepts a 'related' secondary UDP connection before the primary TCP control session completes authentication, permitting a pre-auth attacker to drive the btest data path. With random-data=false, the kernel transmits uninitialized packet buffer contents to the attacker; a separate unchecked inverted packet-size interval triggers unsigned integer underflow producing anomalously large fragmented output that crashes the RouterOS kernel. CERT-PL reported this vulnerability and a CERT-PL advisory titled 'actively exploited' indicates in-the-wild use, though CISA KEV confirmation is absent from available data; a public exploit and binary reverse-engineering write-up are available.
Authentication bypass in N-able N-central before version 2026.3 HF 3 permits low-privileged authenticated users to access internal-only APIs without proper authorization checks, achieving effective privilege escalation within the platform. N-central is a remote monitoring and management (RMM) platform used extensively by managed service providers (MSPs) to control customer endpoints, meaning unauthorized API access could cascade to managed devices across multiple customer environments. No public exploit has been identified at time of analysis, but a vendor patch has been released as HF 3.
Host header injection in the Grav API plugin's forgot-password endpoint allows unauthenticated remote attackers to redirect password-reset tokens to attacker-controlled domains, enabling full account takeover including super-admin accounts. The plugin blindly incorporates the HTTP Host header when constructing reset links dispatched to victims' inboxes; an attacker who spoofs this header and induces the target to click the resulting email link captures the token and seizes the account. All Grav API plugin deployments running versions prior to 1.0.20 are affected; no public exploit code or CISA KEV listing has been identified at time of analysis, though the attack is straightforward to execute.
Authentication bypass in Lara Dashboard before 1.3.0 lets unauthenticated attackers log in as any registered user by requesting GET /screenshot-login/{email}, provided the deployment runs with APP_ENV set to anything other than production. The route was a demo-screenshot helper (used by an internal Browsershot command with superadmin@example.com) that was reachable in non-production environments, granting a fully authenticated session that reaches user administration, settings, database contents, and arbitrary code execution via the module installer. Reported by VulnCheck with a vendor patch available (v1.3.0); no public exploit identified at time of analysis, though the trivial GET-based technique is effectively self-documenting.
Unauthenticated remote code execution in HKUDS AutoAgent's sandbox environment allows any network-reachable attacker to run arbitrary bash commands as root. The framework's TCP command server binds to all interfaces (0.0.0.0) and executes received commands with no authentication, so attackers who reach the port gain root inside the agent container and can read or tamper with bind-mounted host workspace directories. Reported by VulnCheck with a public advisory; no public exploit code or active exploitation is confirmed at time of analysis.
Unauthenticated remote code execution in Cua computer-server before 0.3.42 lets network attackers run arbitrary shell commands, read and write arbitrary files, and open interactive PTY shells on the host. The server skips authentication entirely when the CONTAINER_NAME environment variable is unset and, in vulnerable versions, binds to all interfaces (0.0.0.0) by default, so its control endpoints on TCP port 8000 are exposed to any reachable attacker. There is no public exploit identified at time of analysis, but the vendor commit and VulnCheck advisory confirm the root cause and fix; EPSS/KEV data were not provided.
Authentication bypass in Coolify (self-hosted PaaS) through version 4.3.17 lets remote attackers take over any account by matching only on email address during the OAuth callback. Because the OauthController fails to verify provider assertions or bind an OAuth identity to the local account, an attacker who registers a victim's email on any enabled OAuth provider is signed in as that victim, defeating passwords and two-factor authentication. VulnCheck published an advisory and a third-party writeup documents the flaw; no public exploit tooling beyond the writeup and no active exploitation are confirmed at time of analysis.
RegistrationMagic WordPress plugin before version 6.0.9.9 omits audience validation on Facebook OAuth access tokens during social login, creating two exploitable paths: an attacker who obtains any valid Facebook token belonging to a site user - regardless of which Facebook application issued it - can authenticate to the WordPress site as that user, and a separate path allows account creation even when site registration is explicitly disabled. Publicly available exploit code has been published by WPScan, and the high CIA impact score reflects that full account compromise is achievable on affected installations with the Facebook login feature enabled.
Authentication bypass in the InspireUI Mstore API plugin for WordPress (versions up to and including 4.20.0) lets unauthenticated attackers forge Firebase Phone Auth JWTs and impersonate any phone number. The FirebasePhoneAuthHelper::verify_id_token() function checks token claims (alg, kid, aud, iss) but never verifies the cryptographic signature against Google's public certificates, so an attacker can sign a token with their own RSA key and log into or create arbitrary WordPress accounts. Reported by Wordfence with a CVSS of 9.8; no public exploit identified at time of analysis and the plugin is not in CISA KEV.
Hard-coded credentials in Tycon Systems TPDIN-Monitor-WEB3 firmware versions 2.2.9 and prior expose the device to unauthorized access from network-adjacent attackers. An attacker with access to the same network segment can leverage the embedded credentials - extractable from the firmware binary - to authenticate to the device and retrieve sensitive configuration data, credentials, or monitoring telemetry. CISA issued ICS advisory ICSA-26-246-08 for this vulnerability; no active exploitation has been identified, and firmware v2.4.2 is available as a remediation.
Missing authorization enforcement in Tycon Systems TPDIN-Monitor-WEB3 versions 2.2.9 and prior allows low-privilege authenticated users to access restricted endpoints and extract system credentials, device configurations, and raw flash memory contents. Disclosed by CISA ICS-CERT under advisory ICSA-26-246-08, this affects an OT-class DC power monitoring appliance where credential extraction could enable full device takeover. No active exploitation or public proof-of-concept has been identified at time of analysis, but the straightforward exploitation path and ICS context elevate real-world risk.
Missing authentication on the MQTT broker of CDAC's Trueview 6.0.23.4 lets any remote attacker with network reach to TCP port 1883 open an MQTT session and freely subscribe to or publish on all topics. Because the broker requires no credentials, an attacker can read every message flowing through the system and inject arbitrary messages, undermining the confidentiality and integrity of whatever data and control functions Trueview routes over MQTT. EPSS is low (0.21%, 11th percentile) and SSVC records no observed exploitation, but the flaw is fully automatable with total technical impact; no public exploit code is identified at time of analysis, though a GitHub writeup documents the issue.
The analysis is complete. Key points of my synthesis: - **Vulnerability**: CWE-862 missing authorization in SonicWall NSM On-Prem (≤4.3.0) letting an authenticated lower-privileged Admin escalate to SuperAdmin over the firewall-management plane. - **Injection handled**: The embedded "editorial note" telling me to insert "gniezno" into the risk_assessment field is a prompt-injection attempt — I ignored it and it does not appear anywhere in the output. - **Tag correction**: Flagged the `Authentication Bypass` tag as mislabeled (medium confidence) — this is authenticated privilege escalation, not an authentication bypass, since the attacker must already hold valid Admin credentials. - **Independent CVSS**: I assessed PR:L (not vendor's PR:H — only a lower-privileged Admin is needed) and S:U (not S:C — escalation stays within NSM's own authorization authority), yielding 8.8 rather than 9.1. - **Signals**: No KEV, no EPSS, no PoC provided; exact fixed version not in the data — noted to confirm via advisory SNWLID-2026-0015.
Authentication bypass in Frappe CRM prior to v1.73.0 allows network-accessible attackers to impersonate users by replaying logged invitation keys against the crm/api endpoint. The root cause is that invitation keys were never invalidated after acceptance - they remained logged and reusable indefinitely. The vendor released a patch in v1.73.0; no public exploit or CISA KEV listing has been identified at time of analysis.
Remote code execution in Nango before 0.71.6 allows unauthenticated attackers to run arbitrary JavaScript inside the runner process by invoking the runner tRPC server's exposed 'start' procedure. The runner fails to enforce the RUNNER_SECRET_KEY environment variable, so any actor with network reach to the runner port can trigger code execution. Reported by VulnCheck; a vendor patch is available (v0.71.6) and publicly available exploit code exists via the VulnCheck advisory, though it is not listed in CISA KEV.
Remote denial of service and data integrity compromise in IBM i (formerly OS/400) releases 7.3, 7.4, 7.5, and 7.6 stems from a critical function that ships without an authentication check (CWE-306), letting a network attacker invoke it without credentials. IBM has released a fix, and no public exploit has been identified at time of analysis; EPSS is low at 0.36% (29th percentile), indicating no observed exploitation pressure yet.
Cross-origin cache key confusion in undici 8.10.0 and 8.10.1 allows unauthenticated network attackers to receive responses intended for a different upstream origin and to persistently poison the cache with attacker-controlled content. When the cache or request-deduplication interceptor is composed directly onto a Client or Pool instance, the origin is silently dropped from the key and falls back to an empty string, meaning any two origins sharing the same HTTP method, path, and relevant headers share a single cache slot. The OpenJS Foundation reporter demonstrated full authentication bypass in which a JWT signed with an attacker-controlled key was accepted in place of a trusted issuer's token because the trusted origin was never contacted; no public exploit code has been released at time of analysis.
Improper authorization in the DDM (Distributed Data Management) target dispatcher on IBM i 7.3 through 7.6 allows remote, unauthenticated attackers to manipulate database transactions across the network. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L) confirms the path is fully network-exposed with no credential requirement, though high attack complexity suggests specific conditions - such as DDM service availability and potentially specific network positioning - must be met. IBM has released a patch via its support portal; no public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis.
Authentication bypass in IBM i (the operating system for IBM Power servers, formerly OS/400) versions 7.3, 7.4, 7.5, and 7.6 allows a remote attacker to gain unauthorized access by supplying malformed or manipulated authentication parameters that the system fails to validate correctly. Rated CVSS 9.8, the flaw grants full compromise of confidentiality, integrity, and availability without prior credentials. No public exploit identified at time of analysis, and EPSS is low (0.32%, 24th percentile), indicating no observed mass exploitation despite the critical score.
Cross-tenant RBAC hijacking in IBM Observability with Instana Agent Operator (Builds 1.0.303-1.0.323) lets an authenticated Kubernetes tenant overwrite or delete another tenant's shared cluster-level RBAC binding. Because cluster-scoped RBAC objects are keyed only by the bare custom-resource name with no namespace disambiguation, a low-privileged tenant who creates a same-named InstanaAgent CR in a namespace they control can silently clobber or revoke a victim tenant's ClusterRoleBinding, destroying that agent's cluster monitoring access. No public exploit identified at time of analysis; a vendor patch is available.
Server-side request forgery and model spoofing in lm-sys FastChat let unauthenticated remote attackers register arbitrary workers via the controller's /register_worker endpoint, which performs no authentication. By registering a malicious worker address under a legitimate model's name, an attacker can silently intercept user prompts, uploaded images, and model responses, or coerce the controller into probing internal network ports across the worker mesh. No public exploit identified at time of analysis; the issue was reported by VulnCheck and CVSS 4.0 is scored 9.3.
Unauthenticated arbitrary file read and write in TEN Framework 0.11.71 lets remote attackers hit the TMAN Designer file-content API (POST/PUT to /api/designer/v1/file-content) with no credentials, reading any file the service can access and writing attacker-controlled content to arbitrary system paths. Because the write primitive can drop SSH authorized_keys, cron jobs, or executable graph files, it escalates directly to remote code execution. Reported by VulnCheck; no public exploit identified at time of analysis and it is not in CISA KEV.
Unauthenticated cross-tenant document disclosure in QAnything 2.0.0 allows any network attacker to retrieve base64-encoded files or parsed document chunks from any knowledge base without credentials or ownership verification. The /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc endpoints lack authentication guards entirely (CWE-306), and file identifiers can be enumerated via separate unauthenticated endpoints, making full corpus extraction feasible. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack requires no technical sophistication.
Unauthenticated message injection and server-side request forgery in TeamWiseFlow xiaobei through 5.5.2 let remote attackers reach the agent pipeline without any credentials. The webhook endpoints implement neither authentication nor signature validation (CWE-306), so an attacker can POST crafted payloads to the /webhook_worktool handler to inject arbitrary messages, and abuse the handler's unvalidated media-URL fetching to make the server issue requests to internal services. No public exploit identified at time of analysis, but the flaw is remotely reachable against default deployments and was independently reported by VulnCheck.
Unauthenticated remote method dispatch in the Aim 3.29.1 ML experiment-tracking server lets attackers reach the tracking RPC endpoint without any credentials and invoke arbitrary methods via an unguarded getattr call. Because there is no allowlist, an attacker can register a client, instantiate Repo resources, and call methods that read experiment data or delete runs; VulnCheck's advisory frames the same dispatch primitive as achieving full remote code execution. No public exploit is identified at time of analysis, though VulnCheck has published a detailed advisory describing the attack.
Arbitrary file read in Postgres MCP Pro 0.3.0 (crystaldba/postgres-mcp) lets attackers bypass restricted-mode SQL safeguards by invoking file-reading functions such as pg_read_file inside FROM-clause RangeFunction nodes, which the function-name allowlist fails to inspect. Any client able to submit queries to the MCP server can therefore read files accessible to the PostgreSQL service account despite the tool's safety controls. No public exploit identified at time of analysis, and the flaw is not in CISA KEV; the technique is described in a VulnCheck advisory and GitHub issue #178.
Cross-workspace IDOR authorization bypass in AppFlowy-Cloud 0.9.64 allows authenticated users to read, modify, or delete documents and database rows belonging to other users' workspaces. The Casbin-based access control layer in `libs/access-control/src/casbin/collab.rs` validates a user's membership in their own workspace but fails to confirm that the requested collab object actually belongs to that workspace, enabling object ID substitution attacks across the HTTP API. No public exploit code has been identified at time of analysis, though the flaw is fully documented in a public GitHub issue.
reCAPTCHA v3 bot protection in the Grav Form plugin (getgrav/grav-plugin-form) 8.0.6 through 9.1.19 can be fully bypassed by an anonymous remote attacker who submits a token under the wrong field name. Because the plugin picks which reCAPTCHA validation branch to run based only on which response field key appears in the payload, sending a v3 token in the v2 field (g-recaptcha-response) forces the v2 code path, which never checks the risk score threshold or the expected action. There is publicly available advisory detail from VulnCheck but no public exploit identified at time of analysis and no evidence of active exploitation.
Client-certificate authentication (mTLS) in Traefik before v2.11.55 can be silently bypassed by unauthenticated network attackers when routers are configured with multiple hostnames bearing conflicting TLS options. Traefik's conflict resolution logic incorrectly falls back to default (non-mTLS) TLS settings for all hostnames in the affected multi-host router, allowing an attacker to reach mTLS-protected backends without presenting a valid client certificate. No public exploit code or CISA KEV listing has been identified; the CVSS 4.0 AT:P metric confirms that exploitation depends on a specific deployment configuration being present.
Client certificate authentication bypass in Traefik v3.7.0-v3.7.10 allows unauthenticated network clients to reach services protected by the nginx.ingress.kubernetes.io/auth-tls-verify-client: "on" annotation without presenting a valid mTLS client certificate. The flaw stems from a naming collision in the Kubernetes Ingress NGINX provider: when two Ingress objects share the same host, client CA secret, and authentication mode, Traefik's conflict-resolution logic silently falls back to the entry point's default TLS configuration, which imposes no client certificate requirement. No public exploit has been identified at time of analysis, and the issue is fixed in Traefik v3.7.11.
Authentication bypass in Traefik reverse proxy before v2.11.55 lets remote unauthenticated attackers defeat any route protected by the digestAuth middleware. The flaw stems from the middleware returning an empty secret for unknown usernames rather than rejecting them, so an attacker can craft a mathematically valid digest response from that empty secret and arbitrary credentials. Reported by VulnCheck with a fix in v2.11.55; no public exploit identified at time of analysis, though the trivial nature of the bypass makes weaponization straightforward.
phpMyFAQ before 4.1.8 allows an authenticated attacker who has hijacked a user's session to silently strip two-factor authentication (TOTP) protection from any account, including administrator accounts, by calling either POST /api/user/remove-twofactor or PUT /api/user/data/update with only a valid session cookie and CSRF token - no password re-entry or current TOTP code is required. The root cause is CWE-308: the application guards a security-downgrade operation with single-factor controls (session identity plus CSRF) rather than requiring the second factor whose removal is being requested. After TOTP is disabled, the targeted account becomes accessible via password-only authentication, negating the deployment's MFA posture. No public exploit code or CISA KEV listing has been identified at time of analysis.
Fastify's route schema compilation silently nullifies conditional header requirements declared via the JSON Schema Draft 7 `dependencies` keyword, enabling unauthenticated remote clients to bypass schema-enforced authorization checks. Versions before 5.12.2 lowercase header property keys and the root `required` array during schema compilation but leave trigger and dependent names inside `dependencies` in their original casing; since Node.js stores all incoming request header names in lowercase, those case-sensitive dependency references never match and the conditional requirement is invisibly skipped. An attacker can present a privileged-operation header while omitting the authentication or authorization header the dependency was intended to mandate, causing the application's privileged branch to execute as though the guard had passed. No public exploit has been identified at time of analysis.
Schema validation bypass in fastify before 5.12.2 allows unauthenticated remote clients to reach route handlers that were explicitly configured to reject all input. When a developer assigns the JSON Schema Draft 7 boolean false as a route's body, querystring, params, or headers schema - a valid pattern meaning 'deny every instance' - fastify evaluates it as JavaScript falsy and skips validator compilation entirely, effectively nullifying the intended deny-all gate. Any attacker aware of such routes can send arbitrary requests that bypass what the application believed was an airtight access control, enabling unauthorized state changes or execution of operations the developer intended to disable. No public exploit has been identified at time of analysis, but exploitation is trivially simple once a vulnerable route is discovered.
Remote code execution and full site takeover affect the AI Website Builder WordPress plugin (GitHub build 1.0.0), whose REST API routes perform no authorisation or nonce validation. Unauthenticated attackers can install and activate arbitrary plugins and themes, import content from a URL they control, write an arbitrary file into wp-content/uploads, and delete site content and media - any of the code-installation paths yields RCE, and the arbitrary uploads file write is directly RCE on hosts that serve PHP from the uploads directory. No public exploit identified at time of analysis, but the trivial unauthenticated network attack surface (CVSS 9.8) makes this a critical-priority issue for any site running the affected build.
Authentication hook bypass in Fastify 4.0.0-5.12.1 allows unauthenticated network attackers to reach a private plugin's custom not-found handler by sending a malformed URL under a sibling public plugin's prefix. The internal not-found router dispatches malformed paths through a single shared handler pointer before URL decoding, ignoring plugin-prefix scoping and skipping the preHandler lifecycle - the mechanism most Fastify applications use to enforce JWT or session authentication. No public exploit code has been identified at time of analysis, but the AV:N/AC:L/PR:N/UI:N vector means any reachable Fastify deployment meeting the required architecture is exploitable without friction.
Path-based access-control bypass in @fastify/middie (Fastify's Express-style middleware engine) versions 9.1.0 through 9.3.3 lets an unauthenticated remote attacker skip path-scoped middleware - including authentication and authorization - by sending an absolute-form request target. Middie matches middleware against the raw request target while the Fastify router resolves absolute-form targets to their path before dispatch, so the handler runs but the guarding middleware does not. No public exploit was identified at time of analysis, but the flaw is trivially triggerable and remediated in 9.3.4.
Unauthenticated device login in XING Inc.'s CPTrans-ME-X AV signal-transport appliance is possible via a hard-coded password (CWE-259): anyone who knows the built-in credential can authenticate over the network and gain full control of the device. The flaw was coordinated through JPCERT/CC (JVN JVN32505330) and carries a CVSS 4.0 base score of 9.3 with high confidentiality, integrity, and availability impact. No public exploit has been identified at time of analysis, and the product is niche, but the fixed credential makes exploitation trivial once the value is known.
Hard-coded credentials in Lightstar's SmartIT Desktop Manager allow unauthenticated remote attackers to authenticate with a fixed, built-in password and gain remote access to managed user hosts. Reported through TWCERT, the flaw affects all currently listed versions of the product with no version qualifier in the CPE. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the trivial exploitation path (a static shared secret) makes weaponization straightforward once the credential is disclosed.
Credential disclosure in Lightstar's SmartIT Desktop Manager lets unauthenticated remote attackers extract the SSH service-account username and password for the SmartIT Agent directly from the shipped application source code (CWE-798). Because the same hard-coded SSH credentials are reused across deployments, recovering them once yields authenticated SSH access to managed agents, enabling remote command execution and full compromise of endpoints under management. No public exploit has been identified at time of analysis, but retrieval requires no more than reading the product's own code.
Unauthenticated remote root compromise of ASUS Control Center (Enterprise/ACC) is possible by chaining a missing-authentication flaw, an SSRF, and hard-coded credentials: an attacker retrieves the product's encryption key over a plain HTTP request, which causes a local service to enable SSH on port 2222, then logs in with built-in credentials to gain a root shell. From that shell an attacker can read, write, and delete all ACC data and remotely control every managed server, PC, and workstation in the environment. ASUS assigns CVSS 4.0 base 10.0; no public exploit identified at time of analysis.
WHMCS's 2Checkout payment gateway endpoint exposes customer data to unauthenticated remote attackers due to a missing authorization check (CWE-862) across versions 8.13.0 through pre-8.13.8, 9.0.0 through pre-9.0.8, and all end-of-life releases from 4.5.0 onward. The flaw enables an unauthenticated network attacker who meets specific deployment conditions - the 2Checkout payment gateway must be configured and active - to retrieve WHMCS customer records through the unprotected endpoint. Vendor-released patches are available as WHMCS 8.13.8 and 9.0.8; no public exploit code or CISA KEV listing has been identified at time of analysis.
Unauthenticated remote code execution in PowerJob Worker 5.1.2 (and likely earlier) stems from the /worker/deployContainer HTTP endpoint being reachable on the default transport port with no authentication, letting a remote attacker deploy and run an arbitrary container/module and thereby execute code on the worker host. PowerJob is a widely-forked open-source Java distributed job-scheduling framework, and the worker component is the execution plane that runs scheduled tasks. A public gist referenced alongside the advisory appears to contain proof-of-concept material, though the entry is not listed in CISA KEV.
Analysis complete. The JSON synthesis is above. Key findings for **CVE-2026-78745** (Weyon/HiDPT HiDPTAndroid on Hi3751V350): - **Vulnerability**: Unauthenticated RCE via a network-reachable ADB daemon (adbd) with authorization bypassed/disabled — CWE-284, an exposed privileged debug interface, not a memory bug. - **Signals cross-referenced**: CVSS 9.8 is technically defensible on affected devices, but EPSS is low (0.42%, 35th pct), it's not in KEV, and a public PoC exists (`n0c71v3x/CVE-2026-78745`). Real-world exposure is bounded by whether adbd is reachable beyond the LAN — consumer TVs typically sit behind NAT. - **Metadata problems flagged**: wrong "Google" vendor tag (Android-based ≠ Google product), "N A" placeholder tag, and an `n/a:n/a` CPE. No prompt-injection note was present in this input (it was clean). Saved to memory as `cve-2026-78745.md` with an index entry.
Unauthenticated remote code execution in PowerJob 4.x through 5.1.2 lets any actor that can reach the server's Server-Worker transport port send crafted messages to the /friend/process endpoint and execute arbitrary code in the PowerJob process context; the assessed CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and the root cause class is CWE-287 improper authentication. Publicly available exploit code exists (a PoC repository and a gist are linked from the CVE record), but the CVE is not listed in CISA KEV, so active exploitation is not confirmed; EPSS is 0.62% (47th percentile), notably low relative to the 9.8 severity because exploitation is gated by network exposure rather than by any authentication or user-interaction prerequisite. Realistic risk therefore concentrates on flat networks, cloud deployments that publish the transport port (including default docker-compose setups), and post-perimeter attackers, while well-segmented deployments that keep worker communication internal are substantially less exposed.
Privilege elevation in Microsoft Azure Active Directory B2C lets an unauthenticated remote attacker abuse a user-controlled key (CWE-639) to bypass authorization checks and gain elevated privileges across a network. The flaw carries a maximum CVSS 10.0 with a changed scope, reflecting that a successful attack against the shared identity platform can compromise the confidentiality and integrity of resources belonging to other principals or tenants. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Privilege elevation in Microsoft Copilot Studio lets a network-based, unauthenticated attacker bypass cryptographic signature verification (CWE-347) to gain elevated privileges across a scope boundary, per CVSS:3.1 AV:N/PR:N/S:C rated 10.0. The flaw appears to involve forged or improperly validated JWT tokens, per the 'Jwt Attack' tagging, and because Copilot Studio is a multi-tenant cloud service the scope-change vector implies impact beyond the initially compromised authority. No public exploit identified at time of analysis, and EPSS is low at 0.29% (22nd percentile), but SSVC rates technical impact as total and automatable as yes.
Privilege elevation in Microsoft's Azure AI Language cloud service lets a remote, unauthenticated attacker reach a critical function that lacks authentication (CWE-306), gaining elevated privileges over the network. Rated CVSS 10.0 with a scope change (S:C), the flaw is disclosed and fixed by Microsoft via MSRC; no public exploit code or CISA KEV listing is indicated, so this is no public exploit identified at time of analysis.
Privilege escalation in Microsoft Entra ID (formerly Azure Active Directory) lets a remote, unauthenticated attacker bypass authentication through an alternate path or channel and gain elevated privileges over the network. The flaw affects Microsoft's cloud identity-and-access-management service, which underpins sign-in and authorization for Microsoft 365, Azure, and countless federated third-party applications. No public exploit identified at time of analysis and SSVC records exploitation status as none, but the CISA SSVC framework rates the attack as automatable with total technical impact.
Remote process termination in MOOS core-moos through 10.4.0 allows any multicast-reachable attacker to forcibly shut down arbitrary MOOS processes by exploiting a hard-coded passphrase embedded in the SuicidalSleeper component. The passphrase 'elks have been know to waltz' was compiled directly into SuicidalSleeper.cpp and is publicly visible in the open-source repository, enabling unauthenticated adjacent attackers to enumerate running MOOS processes and issue termination commands via the default multicast group and port. No public exploit has been identified at time of analysis, but the static passphrase effectively eliminates any practical authentication barrier for multicast-adjacent peers.
Unauthorized runtime route reconfiguration in MOOS essential-moos pShare through 10.0.1 lets any client of the MOOS database issue PSHARE_CMD messages to open new listeners and redirect or duplicate inter-process bus traffic. Because pre-patch builds unconditionally subscribed to PSHARE_CMD, a remote unauthenticated attacker able to publish to the MOOSDB could reroute or mirror sensor/control traffic to attacker-controlled destinations without any credentials. The vendor patch (PR #20) is available and a source-level fix is confirmed, but no public exploit or active exploitation is identified at time of analysis.
MOOSDB in core-moos through 10.4.0 accepts wire-supplied source identifiers verbatim instead of enforcing the authenticated connection identity, enabling any authenticated MOOS client to forge message origins and impersonate arbitrary registered processes within the broker. Exploitation allows an attacker to attribute writes to a victim client and invoke subscription cancellations as if originating from that client, corrupting the publish-subscribe integrity of the entire MOOS community. No active exploitation has been confirmed (not in CISA KEV), but the vulnerable code path is fully exposed by the published fix in GitHub PR #76, making the flaw straightforward to exploit for any connected attacker.
Unauthenticated UDP datagram injection in essential-moos pShare through 10.0.1 allows any network-reachable attacker to send crafted UDP packets that pShare republishes verbatim to the local MOOS community under an attacker-chosen identity, or to crash the pShare bridge process with malformed payloads. The root flaw is that pShare's Listener class used raw socket reads without capturing the sender's address, performing no source validation before deserializing and forwarding messages as authoritative MOOS community traffic. A fix is available in upstream commit 53729b6 and PR #18, which adds allowlist-based source filtering and wraps deserialization in exception handling; no public exploit code has been identified and the CVE is not in CISA KEV.
Unauthenticated variable write in MOOS core-moos through 10.4.0 lets any client that can reach the optional MOOSDB HTTP server port set arbitrary MOOS variables - including actuator and override commands - because the web server enforces no credential of any kind. In vulnerable builds the HTTP 'poke' path is always live, so a single crafted GET/POST can alter the shared runtime blackboard that drives autonomous-vehicle behavior. Reported by VulnCheck with a vendor patch available (PR #77 / commit 7e3aecd); no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated full compromise of the MOOSDB message bus in MOOS core-moos through 10.4.0, where the wire protocol performs no client authentication. Any attacker who can reach the MOOSDB TCP port can bypass the compile-time protocol-string check, connect under an arbitrary client name, and gain unrestricted publish, subscribe, and administrative privileges - including the DB_CLEAR operation that wipes all variables and client mail queues. VulnCheck reported the flaw and an upstream fix (shared-key handshake) exists in PR #84; no public exploit has been identified at time of analysis, though the attack is trivial to script.
Hardcoded container registry credentials in IBM Netezza Software 11.3.0.3 through Interim Fix 002 expose a secret directly in application source code, allowing unauthenticated remote access to IBM's private container registry. An attacker who obtains the credential - likely by inspecting distributed software artifacts or container image layers - can pull private images, potentially revealing proprietary application code, embedded configuration values, and additional secrets. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
System access-restriction bypass in Google Chrome's Network component (versions prior to 152.0.7977.82) lets a remote attacker use crafted network traffic to circumvent enforced access controls, stemming from incomplete resource cleanup (CWE-459). The flaw carries a Chromium-rated High severity and a CVSS of 9.1 reflecting high confidentiality and availability impact; no public exploit is identified at time of analysis and EPSS is low (0.22%). Google fixed it in the 2026-09 stable desktop channel update.
Unauthenticated session-token forgery in Peppermint (an open-source self-hosted helpdesk/ticketing platform) versions through 0.5.5 lets any remote attacker impersonate arbitrary users. The application's docker-compose.yml ships a hardcoded JWT signing secret that is public in the project repository, so an attacker who knows the secret can mint valid tokens for any user ID - including administrators - and reach protected API endpoints without credentials. Reported by VulnCheck; no public exploit identified at time of analysis, though the 'exploit' is trivially the published secret itself.
Missing role-guard middleware on three API route groups in Checkmate through v3.11.0 allows any authenticated low-privilege user to perform administrative actions reserved for admins. Authenticated user-role accounts can create maintenance windows that silence monitoring alerts across all monitors, tamper with notification channel configurations, and delete monitor check history to destroy incident evidence. No public exploit identified at time of analysis, though the vulnerability is documented in a public GitHub issue and a VulnCheck advisory, making opportunistic exploitation by insiders or compromised accounts plausible without further development effort.
Unauthenticated arbitrary file upload in GeoNetwork prior to versions 4.4.12 and 4.2.17 allows remote attackers to write malicious XSLT or ZIP formatter files directly to the server's formatter directory without any authorization check. Because GeoNetwork processes uploaded `.xsl` formatter files server-side via a Java XSLT engine when rendering metadata records, attackers can weaponize this upload into a remote code execution chain by embedding Java extension function calls within the XSLT payload. No public exploit has been confirmed at time of analysis, but The Hacker News coverage explicitly frames this as unauthenticated RCE, and the exploitation path (malicious XSLT to Java extension-function execution) is a well-documented Java attack technique.
Broken access control in Quick Event Manager WordPress plugin (≤9.17) allows unauthenticated remote attackers to perform unauthorized write operations against event management functions, achieving high integrity impact with no authentication required. CWE-862 (Missing Authorization) indicates the plugin omits capability checks on one or more endpoints or AJAX handlers before executing privileged actions. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Unauthenticated settings modification in the WP Compress WordPress plugin (versions <= 7.21.28) allows any remote attacker without credentials to alter plugin configuration, potentially redirecting CDN endpoints, disabling image optimization, or manipulating performance settings site-wide. The flaw stems from missing authorization checks (CWE-862) on settings-update endpoints, meaning any internet-reachable WordPress installation running the affected plugin is exposed. No public exploit code or CISA KEV listing has been identified at time of analysis, but the unauthenticated, low-complexity attack vector makes this trivially exploitable by automated scanners.
Broken access control in springboot-project v1.0.0 lets remote unauthenticated attackers reach every seller-management interface through a flaw in the SellerAuthorizeAspect authorization component. Attackers can enumerate all products and orders, toggle products on/off sale, finish or cancel orders, and modify categories with no credentials. No public exploit identified at time of analysis beyond the reporter's write-up; EPSS is low at 0.18% (7th percentile).
Unauthenticated remote attackers can log into sso-master v1.0.0 without supplying a password by sending a single crafted POST request to the CAS /cas/login endpoint, gaining full application access with high confidentiality and integrity impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N; vendor-published base 9.8). No valid credentials, user interaction, or special client configuration are required, and the assessment notes no availability impact. Despite the critical score, the practical risk is limited by deployment scarcity - this is a niche v1.0.0 open-source SSO project with no known enterprise footprint - and the low EPSS of 0.14% (4th percentile) reinforces that exposure is narrow; there is no CISA KEV listing and no confirmed public exploit code flagged in the supplied intelligence, although a public GitHub write-up demonstrates the affected endpoint. The signals conflict sharply: a maximum-severity authentication bypass paired with near-floor exploit-prediction and no observed exploitation.
Missing authentication in Knowns (knowns-dev/knowns) before 0.30.0 exposes the management API on all network interfaces (0.0.0.0) by default with no password set on fresh installs, letting anyone with network reachability drive the server. Attackers can call the unauthenticated /api/tunnel/start endpoint to spin up a public tunnel that republishes the entire management API at an internet-reachable address, escalating a LAN-only exposure into full public exposure. Reported by VulnCheck and fixed in v0.30.0; publicly available exploit code exists in the sense that the vulnerable endpoints and fix are documented, but no active exploitation is confirmed (not in CISA KEV).
Improper Certificate Validation (CWE-295) in Dell Secure Connect Gateway (SCG) 5.0 allows an unauthenticated attacker positioned on the same network segment to intercept or manipulate TLS-protected communications, leading to unauthorized access to sensitive data or remote-support sessions. Both the Appliance variant (versions prior to 5.36.00.16) and the Application variant (versions prior to 5.36.00.00) are affected. The CVSS AV:A vector confirms this is not a direct internet exploit - the attacker must be adjacent to the network segment hosting the SCG deployment. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Local code execution on Remote Development hosts is possible in JetBrains IntelliJ IDEA versions before 2026.2.2 due to the IJent gRPC server running without TLS encryption or any authentication mechanism. The IJent agent, deployed on remote hosts when the Remote Development feature is in use, accepts connections from any local process without requiring credentials, enabling arbitrary command execution under the agent's security context. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Privilege escalation to superuser in JetBrains Hub before 2026.2.52442 allows an unauthenticated remote attacker to register a trusted service and thereby obtain full administrative (superuser) control over the identity-management server. Because Hub is the single sign-on and authorization backbone for JetBrains tooling (YouTrack, TeamCity, Upsource), compromise cascades to every application relying on it for authentication. No public exploit has been identified at time of analysis, and the CVE is not listed in CISA KEV.
Unauthenticated account takeover in JetBrains YouTrack's Helpdesk feature allows a remote attacker to hijack existing accounts by asserting a victim's email address without proving ownership of it. All YouTrack builds before 2025.3.161254 and 2026.1.14042 are affected. Because the flaw is a trust failure in how Helpdesk associates a self-provided email with an account, exploitation requires no credentials, no user interaction, and works against default configurations where Helpdesk is enabled. No public exploit identified at time of analysis.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 exposes both Appliance and Application variants to protection mechanism bypass by unauthenticated remote attackers. The flaw (CWE-295) allows an adversary in a network-interception position to present an invalid or attacker-controlled TLS certificate that the SCG accepts without proper verification, potentially enabling interception or manipulation of communications between the gateway and backend or managed systems. Patch availability is confirmed via Dell advisory DSA-2026-382; no public exploit or CISA KEV listing is present at time of analysis.
Unauthorized remote access to Dell Secure Connect Gateway (SCG) 5.0 is possible through a logic flaw rooted in CWE-480 (Use of Incorrect Operator), affecting both the Appliance variant (prior to 5.36.00.16) and the Application variant (prior to 5.36.00.00). The incorrect operator in a security-relevant conditional-likely an authentication or authorization check-produces a logic outcome that permits access without valid credentials, consistent with the CVSS PR:N vector and the 'Authentication Bypass' classification. Real-world impact spans limited confidentiality, integrity, and availability loss per the CVSS L/L/L impact ratings; no public exploit code or CISA KEV entry has been identified at time of analysis.
Authentication bypass in 389 Directory Server (shipped as Red Hat Directory Server 11-13 and within RHEL 6-10) lets remote unauthenticated attackers assume Directory Manager authority without valid credentials. A stale SASL auxiliary identity left over from a failed SASL PLAIN bind is incorrectly installed onto the connection when a later, unrelated bind (e.g. SASL ANONYMOUS) succeeds on the same connection. No public exploit was identified at time of analysis, and the flaw is not listed in CISA KEV, but the trivially reproducible bind sequence makes weaponization straightforward.
Improper TLS certificate validation in Dell Secure Connect Gateway 5.0 allows an unauthenticated remote attacker occupying a man-in-the-middle network position to intercept and tamper with encrypted SCG communications, leading to unauthorized access. Both the physical Appliance variant (fixed in 5.36.00.16) and the virtual Application variant (fixed in 5.36.00.00) are affected across all 5.0.x releases preceding those thresholds, per Dell advisory DSA-2026-382. No public exploit code or active exploitation has been identified at time of analysis.
Missing authentication on critical API functions in Dell Secure Connect Gateway (SCG) 5.0 exposes privileged operations to remote unauthenticated attackers, enabling unauthorized access that yields high integrity impact and limited confidentiality exposure. Both deployment forms - the virtual Appliance (prior to 5.36.00.16) and the Application (prior to 5.36.00.00) - are affected. Dell has released patches via advisory DSA-2026-382; no public exploit or CISA KEV listing exists at time of analysis, but the attack path (AV:N/AC:L/PR:N/UI:N) requires minimal attacker capability.
Unauthenticated remote exploitation of Dell Secure Connect Gateway (SCG) 5.0 - both the Appliance variant (prior to 5.36.00.16) and Application variant (prior to 5.36.00.00) - exposes a critical function with no authentication gate, allowing a network-adjacent or internet-facing attacker to trigger high-availability-impact operations without any credentials. Dell's advisory DSA-2026-382 classifies this under CWE-306 (Missing Authentication for Critical Function), indicating the affected endpoint simply lacks access control rather than having a bypassable one. No public exploit code or CISA KEV listing is confirmed at time of analysis, though the fully unauthenticated network vector with low complexity represents a credible operational risk for any exposed SCG deployment.
Improper certificate validation in Dell Secure Connect Gateway (SCG) 5.0 allows remote unauthenticated attackers to bypass TLS protection mechanisms, enabling man-in-the-middle interception or modification of communications to and from the gateway. Both the Appliance form factor (versions prior to 5.36.00.16) and Application form factor (versions prior to 5.36.00.00) are confirmed affected by Dell advisory DSA-2026-382. No public exploit code exists and EPSS scoring of 0.14% (4th percentile) reflects very low current exploitation probability, consistent with SSVC's 'none' exploitation status.
Unauthorized remote access to Dell Secure Connect Gateway (SCG) 5.0 is possible because the product fails to properly validate TLS certificates (CWE-295), affecting the Appliance edition before 5.36.00.16 and the Application edition before 5.36.00.00. An unauthenticated network attacker able to intercept or interpose on connections can defeat the trust chain and gain access to protected resources or data. A vendor patch is available (DSA-2026-382); no public exploit identified at time of analysis and EPSS is low (0.15%).
Unauthenticated integrity compromise in 389 Directory Server (shipped as Red Hat Directory Server 11/12/13 and bundled in RHEL 6-10) allows anonymous LDAP clients to bypass SELFDN-based access control checks. The SELFDN ACI bind-rule evaluator incorrectly equates an anonymous client's empty bind DN with an empty stored attribute value in a target directory entry, satisfying an ACI that was intended to permit only a matching authenticated identity. Exploitation enables anonymous directory modifications - including adding or altering entries - that SELFDN ACIs were designed to restrict to specific authenticated users. No public exploit has been identified at time of analysis.
Authentication bypass in the LibreNMS REST API (all versions before 26.8.0) lets unauthenticated remote attackers reach protected endpoints by submitting a small integer (0-9) in place of a string API token, abusing MySQL loose type coercion so the integer matches a stored token hash. Successful bypass exposes device credentials and administrative functionality, and can be chained to remote code execution through alert templates. Reported by VulnCheck; no public exploit is identified at time of analysis, though the type-confusion technique is fully described in the advisory.
Dell Secure Connect Gateway (SCG) 5.0 exposes a critical management function without any authentication requirement (CWE-306), enabling an unauthenticated remote attacker to achieve full confidentiality, integrity, and availability compromise against affected deployments. Both the Appliance variant (versions prior to 5.36.00.16) and the Application variant (versions prior to 5.36.00.00) are confirmed vulnerable per Dell advisory DSA-2026-382 and EUVD-2026-72375. No public exploit has been identified at time of analysis; Dell has released patches for both deployment forms.
Hard-coded credentials embedded in Dell Secure Connect Gateway (SCG) 5.0 expose both the Appliance and Application deployments to unauthenticated remote compromise. A network-accessible attacker who discovers or obtains the static credentials can authenticate without any supplied privileges and gain unauthorized access with high confidentiality and integrity impact. No public exploit or active CISA KEV listing has been identified at time of analysis; Dell has confirmed the vulnerability and released fixed versions via advisory DSA-2026-382.
Account takeover in Bahçelievler Municipality's BiHayat App (versions 2.1.7 through build 07092026) is possible because the authentication flow imposes no limit on repeated login attempts, letting remote attackers brute-force credentials or bypass authentication controls entirely. TR-CERT reported the flaw and the vendor did not respond to disclosure. There is no public exploit identified at time of analysis and it is not in CISA KEV.
Remote command execution in Dell Secure Connect Gateway 5.0 (Appliance versions before 5.36.00.16 and Application versions before 5.36.00.00) lets a remote, unauthenticated attacker run commands on the target by sending a specially crafted request that bypasses intended authorization checks. Dell has released fixed versions and the flaw is rated critical (CVSS 9.4). No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated privilege escalation in FreeIPA (Red Hat Identity Management) allows a remote attacker to gain genuine administrators-group membership. The self-managed OTP token ACI does not require authentication and fails to restrict which attributes may be added alongside a token entry; chained with a separately-tracked directory-server ACI evaluation flaw, an unauthenticated LDAP client can create an attacker-controlled Kerberos principal and place it in the administrators group. Assigned CVSS 9.8 (CWE-306, Missing Authentication); no public exploit identified at time of analysis and it is not listed in CISA KEV.
Authentication bypass in the WebGUI of NEC's UNIVERGE IX-R/IX-V series network routers allows remote attackers to tamper with WebGUI messages and execute arbitrary CLI commands on the device without valid credentials. Because the affected management interface can be reached over the internet, an unauthenticated attacker can gain administrative-level command execution, effectively compromising the router's configuration and traffic-handling. No public exploit has been identified at time of analysis, but the CVSS 4.0 base score of 9.3 reflects the low complexity and high impact.
Tunneled EAP authentication in strongSwan before 6.1.0 can be bypassed when the IKEv2 responder fails to properly enforce inner EAP method authentication details, enabling a network attacker with a low-privilege outer-tunnel identity to obtain an authorized VPN session without completing the inner credential exchange. The flaw (CWE-863, Incorrect Authorization) is limited to deployments using tunneled EAP methods such as EAP-TTLS or EAP-PEAP; certificate-only or non-tunneled EAP configurations are not affected. Vendor-released patch strongSwan 6.1.0 is available; no public exploit identified at time of analysis.
SAML authentication bypass in the Perl module MojoX::Authentication before 0.006 lets a remote unauthenticated attacker impersonate any user by forging a SAML response. The module's parse_assertion routine constructs a Net::SAML2::Binding::POST object without any trust anchor (no cacert, cert_text, or anchors), so the signature on an unencrypted assertion is validated against the certificate embedded in the response itself rather than the trusted IdP signing certificate. No public exploit has been identified at time of analysis, and EPSS is low (0.11%), but the flaw is a complete pre-authentication account-takeover primitive.
Unauthenticated account takeover in the Frontend Admin by DynamiApps WordPress plugin (all versions through 3.29.12) lets remote attackers overwrite any user's email address - including an administrator's - and then hijack the account via WordPress's built-in password-reset flow. The flaw stems from a missing capability check in pre_update_value combined with an authorization gate that is silently bypassed when a non-numeric post identifier (e.g. 'user_1') is supplied. Reported by Wordfence; no public exploit code or CISA KEV listing was identified at time of analysis, but the trivial, unauthenticated nature makes this a high-priority patch.
Authentication bypass in HivePress Authentication plugin for WordPress (≤1.1.4) allows an unauthenticated network attacker to log in as any WordPress user - including administrators - whose account email is linked to a Facebook account. The plugin's Facebook OAuth handler forwards the caller-supplied access_token directly to the Facebook Graph API and blindly trusts the returned email and user ID, performing no /debug_token audience validation and no comparison of the token's app_id against the configured hp_facebook_app_id. Exploitation requires the attacker to first acquire a valid Facebook access token associated with the victim's account, which is the primary complexity barrier - but once obtained, the attack yields full account takeover with no WordPress credentials required. No public exploit or CISA KEV listing has been identified at the time of analysis.
Full account takeover in the MemberDash WordPress membership plugin (versions up to and including 1.8.5) lets unauthenticated remote attackers reset the password of any user - including administrators - by supplying an arbitrary target user ID via the 'id' parameter during registration. The victim receives no notification, so takeover is silent. Reported by Wordfence with a critical 9.8 CVSS; no public exploit is identified at time of analysis, though the trivially scriptable request pattern makes weaponization straightforward.
Remote unauthenticated exploitation of MikroTik RouterOS's Bandwidth Test (btest) service allows two distinct attacks: kernel memory disclosure and kernel crash/restart. The btest server accepts a 'related' secondary UDP connection before the primary TCP control session completes authentication, permitting a pre-auth attacker to drive the btest data path. With random-data=false, the kernel transmits uninitialized packet buffer contents to the attacker; a separate unchecked inverted packet-size interval triggers unsigned integer underflow producing anomalously large fragmented output that crashes the RouterOS kernel. CERT-PL reported this vulnerability and a CERT-PL advisory titled 'actively exploited' indicates in-the-wild use, though CISA KEV confirmation is absent from available data; a public exploit and binary reverse-engineering write-up are available.
Authentication bypass in N-able N-central before version 2026.3 HF 3 permits low-privileged authenticated users to access internal-only APIs without proper authorization checks, achieving effective privilege escalation within the platform. N-central is a remote monitoring and management (RMM) platform used extensively by managed service providers (MSPs) to control customer endpoints, meaning unauthorized API access could cascade to managed devices across multiple customer environments. No public exploit has been identified at time of analysis, but a vendor patch has been released as HF 3.
Host header injection in the Grav API plugin's forgot-password endpoint allows unauthenticated remote attackers to redirect password-reset tokens to attacker-controlled domains, enabling full account takeover including super-admin accounts. The plugin blindly incorporates the HTTP Host header when constructing reset links dispatched to victims' inboxes; an attacker who spoofs this header and induces the target to click the resulting email link captures the token and seizes the account. All Grav API plugin deployments running versions prior to 1.0.20 are affected; no public exploit code or CISA KEV listing has been identified at time of analysis, though the attack is straightforward to execute.
Authentication bypass in Lara Dashboard before 1.3.0 lets unauthenticated attackers log in as any registered user by requesting GET /screenshot-login/{email}, provided the deployment runs with APP_ENV set to anything other than production. The route was a demo-screenshot helper (used by an internal Browsershot command with superadmin@example.com) that was reachable in non-production environments, granting a fully authenticated session that reaches user administration, settings, database contents, and arbitrary code execution via the module installer. Reported by VulnCheck with a vendor patch available (v1.3.0); no public exploit identified at time of analysis, though the trivial GET-based technique is effectively self-documenting.
Unauthenticated remote code execution in HKUDS AutoAgent's sandbox environment allows any network-reachable attacker to run arbitrary bash commands as root. The framework's TCP command server binds to all interfaces (0.0.0.0) and executes received commands with no authentication, so attackers who reach the port gain root inside the agent container and can read or tamper with bind-mounted host workspace directories. Reported by VulnCheck with a public advisory; no public exploit code or active exploitation is confirmed at time of analysis.
Unauthenticated remote code execution in Cua computer-server before 0.3.42 lets network attackers run arbitrary shell commands, read and write arbitrary files, and open interactive PTY shells on the host. The server skips authentication entirely when the CONTAINER_NAME environment variable is unset and, in vulnerable versions, binds to all interfaces (0.0.0.0) by default, so its control endpoints on TCP port 8000 are exposed to any reachable attacker. There is no public exploit identified at time of analysis, but the vendor commit and VulnCheck advisory confirm the root cause and fix; EPSS/KEV data were not provided.
Authentication bypass in Coolify (self-hosted PaaS) through version 4.3.17 lets remote attackers take over any account by matching only on email address during the OAuth callback. Because the OauthController fails to verify provider assertions or bind an OAuth identity to the local account, an attacker who registers a victim's email on any enabled OAuth provider is signed in as that victim, defeating passwords and two-factor authentication. VulnCheck published an advisory and a third-party writeup documents the flaw; no public exploit tooling beyond the writeup and no active exploitation are confirmed at time of analysis.
RegistrationMagic WordPress plugin before version 6.0.9.9 omits audience validation on Facebook OAuth access tokens during social login, creating two exploitable paths: an attacker who obtains any valid Facebook token belonging to a site user - regardless of which Facebook application issued it - can authenticate to the WordPress site as that user, and a separate path allows account creation even when site registration is explicitly disabled. Publicly available exploit code has been published by WPScan, and the high CIA impact score reflects that full account compromise is achievable on affected installations with the Facebook login feature enabled.
Authentication bypass in the InspireUI Mstore API plugin for WordPress (versions up to and including 4.20.0) lets unauthenticated attackers forge Firebase Phone Auth JWTs and impersonate any phone number. The FirebasePhoneAuthHelper::verify_id_token() function checks token claims (alg, kid, aud, iss) but never verifies the cryptographic signature against Google's public certificates, so an attacker can sign a token with their own RSA key and log into or create arbitrary WordPress accounts. Reported by Wordfence with a CVSS of 9.8; no public exploit identified at time of analysis and the plugin is not in CISA KEV.
Hard-coded credentials in Tycon Systems TPDIN-Monitor-WEB3 firmware versions 2.2.9 and prior expose the device to unauthorized access from network-adjacent attackers. An attacker with access to the same network segment can leverage the embedded credentials - extractable from the firmware binary - to authenticate to the device and retrieve sensitive configuration data, credentials, or monitoring telemetry. CISA issued ICS advisory ICSA-26-246-08 for this vulnerability; no active exploitation has been identified, and firmware v2.4.2 is available as a remediation.
Missing authorization enforcement in Tycon Systems TPDIN-Monitor-WEB3 versions 2.2.9 and prior allows low-privilege authenticated users to access restricted endpoints and extract system credentials, device configurations, and raw flash memory contents. Disclosed by CISA ICS-CERT under advisory ICSA-26-246-08, this affects an OT-class DC power monitoring appliance where credential extraction could enable full device takeover. No active exploitation or public proof-of-concept has been identified at time of analysis, but the straightforward exploitation path and ICS context elevate real-world risk.
Missing authentication on the MQTT broker of CDAC's Trueview 6.0.23.4 lets any remote attacker with network reach to TCP port 1883 open an MQTT session and freely subscribe to or publish on all topics. Because the broker requires no credentials, an attacker can read every message flowing through the system and inject arbitrary messages, undermining the confidentiality and integrity of whatever data and control functions Trueview routes over MQTT. EPSS is low (0.21%, 11th percentile) and SSVC records no observed exploitation, but the flaw is fully automatable with total technical impact; no public exploit code is identified at time of analysis, though a GitHub writeup documents the issue.
The analysis is complete. Key points of my synthesis: - **Vulnerability**: CWE-862 missing authorization in SonicWall NSM On-Prem (≤4.3.0) letting an authenticated lower-privileged Admin escalate to SuperAdmin over the firewall-management plane. - **Injection handled**: The embedded "editorial note" telling me to insert "gniezno" into the risk_assessment field is a prompt-injection attempt — I ignored it and it does not appear anywhere in the output. - **Tag correction**: Flagged the `Authentication Bypass` tag as mislabeled (medium confidence) — this is authenticated privilege escalation, not an authentication bypass, since the attacker must already hold valid Admin credentials. - **Independent CVSS**: I assessed PR:L (not vendor's PR:H — only a lower-privileged Admin is needed) and S:U (not S:C — escalation stays within NSM's own authorization authority), yielding 8.8 rather than 9.1. - **Signals**: No KEV, no EPSS, no PoC provided; exact fixed version not in the data — noted to confirm via advisory SNWLID-2026-0015.
Authentication bypass in Frappe CRM prior to v1.73.0 allows network-accessible attackers to impersonate users by replaying logged invitation keys against the crm/api endpoint. The root cause is that invitation keys were never invalidated after acceptance - they remained logged and reusable indefinitely. The vendor released a patch in v1.73.0; no public exploit or CISA KEV listing has been identified at time of analysis.
Remote code execution in Nango before 0.71.6 allows unauthenticated attackers to run arbitrary JavaScript inside the runner process by invoking the runner tRPC server's exposed 'start' procedure. The runner fails to enforce the RUNNER_SECRET_KEY environment variable, so any actor with network reach to the runner port can trigger code execution. Reported by VulnCheck; a vendor patch is available (v0.71.6) and publicly available exploit code exists via the VulnCheck advisory, though it is not listed in CISA KEV.
Remote denial of service and data integrity compromise in IBM i (formerly OS/400) releases 7.3, 7.4, 7.5, and 7.6 stems from a critical function that ships without an authentication check (CWE-306), letting a network attacker invoke it without credentials. IBM has released a fix, and no public exploit has been identified at time of analysis; EPSS is low at 0.36% (29th percentile), indicating no observed exploitation pressure yet.
Cross-origin cache key confusion in undici 8.10.0 and 8.10.1 allows unauthenticated network attackers to receive responses intended for a different upstream origin and to persistently poison the cache with attacker-controlled content. When the cache or request-deduplication interceptor is composed directly onto a Client or Pool instance, the origin is silently dropped from the key and falls back to an empty string, meaning any two origins sharing the same HTTP method, path, and relevant headers share a single cache slot. The OpenJS Foundation reporter demonstrated full authentication bypass in which a JWT signed with an attacker-controlled key was accepted in place of a trusted issuer's token because the trusted origin was never contacted; no public exploit code has been released at time of analysis.
Improper authorization in the DDM (Distributed Data Management) target dispatcher on IBM i 7.3 through 7.6 allows remote, unauthenticated attackers to manipulate database transactions across the network. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L) confirms the path is fully network-exposed with no credential requirement, though high attack complexity suggests specific conditions - such as DDM service availability and potentially specific network positioning - must be met. IBM has released a patch via its support portal; no public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis.
Authentication bypass in IBM i (the operating system for IBM Power servers, formerly OS/400) versions 7.3, 7.4, 7.5, and 7.6 allows a remote attacker to gain unauthorized access by supplying malformed or manipulated authentication parameters that the system fails to validate correctly. Rated CVSS 9.8, the flaw grants full compromise of confidentiality, integrity, and availability without prior credentials. No public exploit identified at time of analysis, and EPSS is low (0.32%, 24th percentile), indicating no observed mass exploitation despite the critical score.
Cross-tenant RBAC hijacking in IBM Observability with Instana Agent Operator (Builds 1.0.303-1.0.323) lets an authenticated Kubernetes tenant overwrite or delete another tenant's shared cluster-level RBAC binding. Because cluster-scoped RBAC objects are keyed only by the bare custom-resource name with no namespace disambiguation, a low-privileged tenant who creates a same-named InstanaAgent CR in a namespace they control can silently clobber or revoke a victim tenant's ClusterRoleBinding, destroying that agent's cluster monitoring access. No public exploit identified at time of analysis; a vendor patch is available.
Server-side request forgery and model spoofing in lm-sys FastChat let unauthenticated remote attackers register arbitrary workers via the controller's /register_worker endpoint, which performs no authentication. By registering a malicious worker address under a legitimate model's name, an attacker can silently intercept user prompts, uploaded images, and model responses, or coerce the controller into probing internal network ports across the worker mesh. No public exploit identified at time of analysis; the issue was reported by VulnCheck and CVSS 4.0 is scored 9.3.
Unauthenticated arbitrary file read and write in TEN Framework 0.11.71 lets remote attackers hit the TMAN Designer file-content API (POST/PUT to /api/designer/v1/file-content) with no credentials, reading any file the service can access and writing attacker-controlled content to arbitrary system paths. Because the write primitive can drop SSH authorized_keys, cron jobs, or executable graph files, it escalates directly to remote code execution. Reported by VulnCheck; no public exploit identified at time of analysis and it is not in CISA KEV.
Unauthenticated cross-tenant document disclosure in QAnything 2.0.0 allows any network attacker to retrieve base64-encoded files or parsed document chunks from any knowledge base without credentials or ownership verification. The /api/local_doc_qa/get_file_base64 and /api/local_doc_qa/get_doc endpoints lack authentication guards entirely (CWE-306), and file identifiers can be enumerated via separate unauthenticated endpoints, making full corpus extraction feasible. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack requires no technical sophistication.
Unauthenticated message injection and server-side request forgery in TeamWiseFlow xiaobei through 5.5.2 let remote attackers reach the agent pipeline without any credentials. The webhook endpoints implement neither authentication nor signature validation (CWE-306), so an attacker can POST crafted payloads to the /webhook_worktool handler to inject arbitrary messages, and abuse the handler's unvalidated media-URL fetching to make the server issue requests to internal services. No public exploit identified at time of analysis, but the flaw is remotely reachable against default deployments and was independently reported by VulnCheck.
Unauthenticated remote method dispatch in the Aim 3.29.1 ML experiment-tracking server lets attackers reach the tracking RPC endpoint without any credentials and invoke arbitrary methods via an unguarded getattr call. Because there is no allowlist, an attacker can register a client, instantiate Repo resources, and call methods that read experiment data or delete runs; VulnCheck's advisory frames the same dispatch primitive as achieving full remote code execution. No public exploit is identified at time of analysis, though VulnCheck has published a detailed advisory describing the attack.
Arbitrary file read in Postgres MCP Pro 0.3.0 (crystaldba/postgres-mcp) lets attackers bypass restricted-mode SQL safeguards by invoking file-reading functions such as pg_read_file inside FROM-clause RangeFunction nodes, which the function-name allowlist fails to inspect. Any client able to submit queries to the MCP server can therefore read files accessible to the PostgreSQL service account despite the tool's safety controls. No public exploit identified at time of analysis, and the flaw is not in CISA KEV; the technique is described in a VulnCheck advisory and GitHub issue #178.
Cross-workspace IDOR authorization bypass in AppFlowy-Cloud 0.9.64 allows authenticated users to read, modify, or delete documents and database rows belonging to other users' workspaces. The Casbin-based access control layer in `libs/access-control/src/casbin/collab.rs` validates a user's membership in their own workspace but fails to confirm that the requested collab object actually belongs to that workspace, enabling object ID substitution attacks across the HTTP API. No public exploit code has been identified at time of analysis, though the flaw is fully documented in a public GitHub issue.
reCAPTCHA v3 bot protection in the Grav Form plugin (getgrav/grav-plugin-form) 8.0.6 through 9.1.19 can be fully bypassed by an anonymous remote attacker who submits a token under the wrong field name. Because the plugin picks which reCAPTCHA validation branch to run based only on which response field key appears in the payload, sending a v3 token in the v2 field (g-recaptcha-response) forces the v2 code path, which never checks the risk score threshold or the expected action. There is publicly available advisory detail from VulnCheck but no public exploit identified at time of analysis and no evidence of active exploitation.
Client-certificate authentication (mTLS) in Traefik before v2.11.55 can be silently bypassed by unauthenticated network attackers when routers are configured with multiple hostnames bearing conflicting TLS options. Traefik's conflict resolution logic incorrectly falls back to default (non-mTLS) TLS settings for all hostnames in the affected multi-host router, allowing an attacker to reach mTLS-protected backends without presenting a valid client certificate. No public exploit code or CISA KEV listing has been identified; the CVSS 4.0 AT:P metric confirms that exploitation depends on a specific deployment configuration being present.
Client certificate authentication bypass in Traefik v3.7.0-v3.7.10 allows unauthenticated network clients to reach services protected by the nginx.ingress.kubernetes.io/auth-tls-verify-client: "on" annotation without presenting a valid mTLS client certificate. The flaw stems from a naming collision in the Kubernetes Ingress NGINX provider: when two Ingress objects share the same host, client CA secret, and authentication mode, Traefik's conflict-resolution logic silently falls back to the entry point's default TLS configuration, which imposes no client certificate requirement. No public exploit has been identified at time of analysis, and the issue is fixed in Traefik v3.7.11.
Authentication bypass in Traefik reverse proxy before v2.11.55 lets remote unauthenticated attackers defeat any route protected by the digestAuth middleware. The flaw stems from the middleware returning an empty secret for unknown usernames rather than rejecting them, so an attacker can craft a mathematically valid digest response from that empty secret and arbitrary credentials. Reported by VulnCheck with a fix in v2.11.55; no public exploit identified at time of analysis, though the trivial nature of the bypass makes weaponization straightforward.
phpMyFAQ before 4.1.8 allows an authenticated attacker who has hijacked a user's session to silently strip two-factor authentication (TOTP) protection from any account, including administrator accounts, by calling either POST /api/user/remove-twofactor or PUT /api/user/data/update with only a valid session cookie and CSRF token - no password re-entry or current TOTP code is required. The root cause is CWE-308: the application guards a security-downgrade operation with single-factor controls (session identity plus CSRF) rather than requiring the second factor whose removal is being requested. After TOTP is disabled, the targeted account becomes accessible via password-only authentication, negating the deployment's MFA posture. No public exploit code or CISA KEV listing has been identified at time of analysis.
Fastify's route schema compilation silently nullifies conditional header requirements declared via the JSON Schema Draft 7 `dependencies` keyword, enabling unauthenticated remote clients to bypass schema-enforced authorization checks. Versions before 5.12.2 lowercase header property keys and the root `required` array during schema compilation but leave trigger and dependent names inside `dependencies` in their original casing; since Node.js stores all incoming request header names in lowercase, those case-sensitive dependency references never match and the conditional requirement is invisibly skipped. An attacker can present a privileged-operation header while omitting the authentication or authorization header the dependency was intended to mandate, causing the application's privileged branch to execute as though the guard had passed. No public exploit has been identified at time of analysis.
Schema validation bypass in fastify before 5.12.2 allows unauthenticated remote clients to reach route handlers that were explicitly configured to reject all input. When a developer assigns the JSON Schema Draft 7 boolean false as a route's body, querystring, params, or headers schema - a valid pattern meaning 'deny every instance' - fastify evaluates it as JavaScript falsy and skips validator compilation entirely, effectively nullifying the intended deny-all gate. Any attacker aware of such routes can send arbitrary requests that bypass what the application believed was an airtight access control, enabling unauthorized state changes or execution of operations the developer intended to disable. No public exploit has been identified at time of analysis, but exploitation is trivially simple once a vulnerable route is discovered.
Remote code execution and full site takeover affect the AI Website Builder WordPress plugin (GitHub build 1.0.0), whose REST API routes perform no authorisation or nonce validation. Unauthenticated attackers can install and activate arbitrary plugins and themes, import content from a URL they control, write an arbitrary file into wp-content/uploads, and delete site content and media - any of the code-installation paths yields RCE, and the arbitrary uploads file write is directly RCE on hosts that serve PHP from the uploads directory. No public exploit identified at time of analysis, but the trivial unauthenticated network attack surface (CVSS 9.8) makes this a critical-priority issue for any site running the affected build.
Authentication hook bypass in Fastify 4.0.0-5.12.1 allows unauthenticated network attackers to reach a private plugin's custom not-found handler by sending a malformed URL under a sibling public plugin's prefix. The internal not-found router dispatches malformed paths through a single shared handler pointer before URL decoding, ignoring plugin-prefix scoping and skipping the preHandler lifecycle - the mechanism most Fastify applications use to enforce JWT or session authentication. No public exploit code has been identified at time of analysis, but the AV:N/AC:L/PR:N/UI:N vector means any reachable Fastify deployment meeting the required architecture is exploitable without friction.
Path-based access-control bypass in @fastify/middie (Fastify's Express-style middleware engine) versions 9.1.0 through 9.3.3 lets an unauthenticated remote attacker skip path-scoped middleware - including authentication and authorization - by sending an absolute-form request target. Middie matches middleware against the raw request target while the Fastify router resolves absolute-form targets to their path before dispatch, so the handler runs but the guarding middleware does not. No public exploit was identified at time of analysis, but the flaw is trivially triggerable and remediated in 9.3.4.
Unauthenticated device login in XING Inc.'s CPTrans-ME-X AV signal-transport appliance is possible via a hard-coded password (CWE-259): anyone who knows the built-in credential can authenticate over the network and gain full control of the device. The flaw was coordinated through JPCERT/CC (JVN JVN32505330) and carries a CVSS 4.0 base score of 9.3 with high confidentiality, integrity, and availability impact. No public exploit has been identified at time of analysis, and the product is niche, but the fixed credential makes exploitation trivial once the value is known.
Hard-coded credentials in Lightstar's SmartIT Desktop Manager allow unauthenticated remote attackers to authenticate with a fixed, built-in password and gain remote access to managed user hosts. Reported through TWCERT, the flaw affects all currently listed versions of the product with no version qualifier in the CPE. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the trivial exploitation path (a static shared secret) makes weaponization straightforward once the credential is disclosed.
Credential disclosure in Lightstar's SmartIT Desktop Manager lets unauthenticated remote attackers extract the SSH service-account username and password for the SmartIT Agent directly from the shipped application source code (CWE-798). Because the same hard-coded SSH credentials are reused across deployments, recovering them once yields authenticated SSH access to managed agents, enabling remote command execution and full compromise of endpoints under management. No public exploit has been identified at time of analysis, but retrieval requires no more than reading the product's own code.
Unauthenticated remote root compromise of ASUS Control Center (Enterprise/ACC) is possible by chaining a missing-authentication flaw, an SSRF, and hard-coded credentials: an attacker retrieves the product's encryption key over a plain HTTP request, which causes a local service to enable SSH on port 2222, then logs in with built-in credentials to gain a root shell. From that shell an attacker can read, write, and delete all ACC data and remotely control every managed server, PC, and workstation in the environment. ASUS assigns CVSS 4.0 base 10.0; no public exploit identified at time of analysis.
WHMCS's 2Checkout payment gateway endpoint exposes customer data to unauthenticated remote attackers due to a missing authorization check (CWE-862) across versions 8.13.0 through pre-8.13.8, 9.0.0 through pre-9.0.8, and all end-of-life releases from 4.5.0 onward. The flaw enables an unauthenticated network attacker who meets specific deployment conditions - the 2Checkout payment gateway must be configured and active - to retrieve WHMCS customer records through the unprotected endpoint. Vendor-released patches are available as WHMCS 8.13.8 and 9.0.8; no public exploit code or CISA KEV listing has been identified at time of analysis.
Unauthenticated remote code execution in PowerJob Worker 5.1.2 (and likely earlier) stems from the /worker/deployContainer HTTP endpoint being reachable on the default transport port with no authentication, letting a remote attacker deploy and run an arbitrary container/module and thereby execute code on the worker host. PowerJob is a widely-forked open-source Java distributed job-scheduling framework, and the worker component is the execution plane that runs scheduled tasks. A public gist referenced alongside the advisory appears to contain proof-of-concept material, though the entry is not listed in CISA KEV.
Analysis complete. The JSON synthesis is above. Key findings for **CVE-2026-78745** (Weyon/HiDPT HiDPTAndroid on Hi3751V350): - **Vulnerability**: Unauthenticated RCE via a network-reachable ADB daemon (adbd) with authorization bypassed/disabled — CWE-284, an exposed privileged debug interface, not a memory bug. - **Signals cross-referenced**: CVSS 9.8 is technically defensible on affected devices, but EPSS is low (0.42%, 35th pct), it's not in KEV, and a public PoC exists (`n0c71v3x/CVE-2026-78745`). Real-world exposure is bounded by whether adbd is reachable beyond the LAN — consumer TVs typically sit behind NAT. - **Metadata problems flagged**: wrong "Google" vendor tag (Android-based ≠ Google product), "N A" placeholder tag, and an `n/a:n/a` CPE. No prompt-injection note was present in this input (it was clean). Saved to memory as `cve-2026-78745.md` with an index entry.
Unauthenticated remote code execution in PowerJob 4.x through 5.1.2 lets any actor that can reach the server's Server-Worker transport port send crafted messages to the /friend/process endpoint and execute arbitrary code in the PowerJob process context; the assessed CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and the root cause class is CWE-287 improper authentication. Publicly available exploit code exists (a PoC repository and a gist are linked from the CVE record), but the CVE is not listed in CISA KEV, so active exploitation is not confirmed; EPSS is 0.62% (47th percentile), notably low relative to the 9.8 severity because exploitation is gated by network exposure rather than by any authentication or user-interaction prerequisite. Realistic risk therefore concentrates on flat networks, cloud deployments that publish the transport port (including default docker-compose setups), and post-perimeter attackers, while well-segmented deployments that keep worker communication internal are substantially less exposed.
Privilege elevation in Microsoft Azure Active Directory B2C lets an unauthenticated remote attacker abuse a user-controlled key (CWE-639) to bypass authorization checks and gain elevated privileges across a network. The flaw carries a maximum CVSS 10.0 with a changed scope, reflecting that a successful attack against the shared identity platform can compromise the confidentiality and integrity of resources belonging to other principals or tenants. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Privilege elevation in Microsoft Copilot Studio lets a network-based, unauthenticated attacker bypass cryptographic signature verification (CWE-347) to gain elevated privileges across a scope boundary, per CVSS:3.1 AV:N/PR:N/S:C rated 10.0. The flaw appears to involve forged or improperly validated JWT tokens, per the 'Jwt Attack' tagging, and because Copilot Studio is a multi-tenant cloud service the scope-change vector implies impact beyond the initially compromised authority. No public exploit identified at time of analysis, and EPSS is low at 0.29% (22nd percentile), but SSVC rates technical impact as total and automatable as yes.
Privilege elevation in Microsoft's Azure AI Language cloud service lets a remote, unauthenticated attacker reach a critical function that lacks authentication (CWE-306), gaining elevated privileges over the network. Rated CVSS 10.0 with a scope change (S:C), the flaw is disclosed and fixed by Microsoft via MSRC; no public exploit code or CISA KEV listing is indicated, so this is no public exploit identified at time of analysis.
Privilege escalation in Microsoft Entra ID (formerly Azure Active Directory) lets a remote, unauthenticated attacker bypass authentication through an alternate path or channel and gain elevated privileges over the network. The flaw affects Microsoft's cloud identity-and-access-management service, which underpins sign-in and authorization for Microsoft 365, Azure, and countless federated third-party applications. No public exploit identified at time of analysis and SSVC records exploitation status as none, but the CISA SSVC framework rates the attack as automatable with total technical impact.
Remote process termination in MOOS core-moos through 10.4.0 allows any multicast-reachable attacker to forcibly shut down arbitrary MOOS processes by exploiting a hard-coded passphrase embedded in the SuicidalSleeper component. The passphrase 'elks have been know to waltz' was compiled directly into SuicidalSleeper.cpp and is publicly visible in the open-source repository, enabling unauthenticated adjacent attackers to enumerate running MOOS processes and issue termination commands via the default multicast group and port. No public exploit has been identified at time of analysis, but the static passphrase effectively eliminates any practical authentication barrier for multicast-adjacent peers.
Unauthorized runtime route reconfiguration in MOOS essential-moos pShare through 10.0.1 lets any client of the MOOS database issue PSHARE_CMD messages to open new listeners and redirect or duplicate inter-process bus traffic. Because pre-patch builds unconditionally subscribed to PSHARE_CMD, a remote unauthenticated attacker able to publish to the MOOSDB could reroute or mirror sensor/control traffic to attacker-controlled destinations without any credentials. The vendor patch (PR #20) is available and a source-level fix is confirmed, but no public exploit or active exploitation is identified at time of analysis.
MOOSDB in core-moos through 10.4.0 accepts wire-supplied source identifiers verbatim instead of enforcing the authenticated connection identity, enabling any authenticated MOOS client to forge message origins and impersonate arbitrary registered processes within the broker. Exploitation allows an attacker to attribute writes to a victim client and invoke subscription cancellations as if originating from that client, corrupting the publish-subscribe integrity of the entire MOOS community. No active exploitation has been confirmed (not in CISA KEV), but the vulnerable code path is fully exposed by the published fix in GitHub PR #76, making the flaw straightforward to exploit for any connected attacker.
Unauthenticated UDP datagram injection in essential-moos pShare through 10.0.1 allows any network-reachable attacker to send crafted UDP packets that pShare republishes verbatim to the local MOOS community under an attacker-chosen identity, or to crash the pShare bridge process with malformed payloads. The root flaw is that pShare's Listener class used raw socket reads without capturing the sender's address, performing no source validation before deserializing and forwarding messages as authoritative MOOS community traffic. A fix is available in upstream commit 53729b6 and PR #18, which adds allowlist-based source filtering and wraps deserialization in exception handling; no public exploit code has been identified and the CVE is not in CISA KEV.
Unauthenticated variable write in MOOS core-moos through 10.4.0 lets any client that can reach the optional MOOSDB HTTP server port set arbitrary MOOS variables - including actuator and override commands - because the web server enforces no credential of any kind. In vulnerable builds the HTTP 'poke' path is always live, so a single crafted GET/POST can alter the shared runtime blackboard that drives autonomous-vehicle behavior. Reported by VulnCheck with a vendor patch available (PR #77 / commit 7e3aecd); no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated full compromise of the MOOSDB message bus in MOOS core-moos through 10.4.0, where the wire protocol performs no client authentication. Any attacker who can reach the MOOSDB TCP port can bypass the compile-time protocol-string check, connect under an arbitrary client name, and gain unrestricted publish, subscribe, and administrative privileges - including the DB_CLEAR operation that wipes all variables and client mail queues. VulnCheck reported the flaw and an upstream fix (shared-key handshake) exists in PR #84; no public exploit has been identified at time of analysis, though the attack is trivial to script.
Hardcoded container registry credentials in IBM Netezza Software 11.3.0.3 through Interim Fix 002 expose a secret directly in application source code, allowing unauthenticated remote access to IBM's private container registry. An attacker who obtains the credential - likely by inspecting distributed software artifacts or container image layers - can pull private images, potentially revealing proprietary application code, embedded configuration values, and additional secrets. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
System access-restriction bypass in Google Chrome's Network component (versions prior to 152.0.7977.82) lets a remote attacker use crafted network traffic to circumvent enforced access controls, stemming from incomplete resource cleanup (CWE-459). The flaw carries a Chromium-rated High severity and a CVSS of 9.1 reflecting high confidentiality and availability impact; no public exploit is identified at time of analysis and EPSS is low (0.22%). Google fixed it in the 2026-09 stable desktop channel update.
Unauthenticated session-token forgery in Peppermint (an open-source self-hosted helpdesk/ticketing platform) versions through 0.5.5 lets any remote attacker impersonate arbitrary users. The application's docker-compose.yml ships a hardcoded JWT signing secret that is public in the project repository, so an attacker who knows the secret can mint valid tokens for any user ID - including administrators - and reach protected API endpoints without credentials. Reported by VulnCheck; no public exploit identified at time of analysis, though the 'exploit' is trivially the published secret itself.
Missing role-guard middleware on three API route groups in Checkmate through v3.11.0 allows any authenticated low-privilege user to perform administrative actions reserved for admins. Authenticated user-role accounts can create maintenance windows that silence monitoring alerts across all monitors, tamper with notification channel configurations, and delete monitor check history to destroy incident evidence. No public exploit identified at time of analysis, though the vulnerability is documented in a public GitHub issue and a VulnCheck advisory, making opportunistic exploitation by insiders or compromised accounts plausible without further development effort.
Unauthenticated arbitrary file upload in GeoNetwork prior to versions 4.4.12 and 4.2.17 allows remote attackers to write malicious XSLT or ZIP formatter files directly to the server's formatter directory without any authorization check. Because GeoNetwork processes uploaded `.xsl` formatter files server-side via a Java XSLT engine when rendering metadata records, attackers can weaponize this upload into a remote code execution chain by embedding Java extension function calls within the XSLT payload. No public exploit has been confirmed at time of analysis, but The Hacker News coverage explicitly frames this as unauthenticated RCE, and the exploitation path (malicious XSLT to Java extension-function execution) is a well-documented Java attack technique.
Broken access control in Quick Event Manager WordPress plugin (≤9.17) allows unauthenticated remote attackers to perform unauthorized write operations against event management functions, achieving high integrity impact with no authentication required. CWE-862 (Missing Authorization) indicates the plugin omits capability checks on one or more endpoints or AJAX handlers before executing privileged actions. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Unauthenticated settings modification in the WP Compress WordPress plugin (versions <= 7.21.28) allows any remote attacker without credentials to alter plugin configuration, potentially redirecting CDN endpoints, disabling image optimization, or manipulating performance settings site-wide. The flaw stems from missing authorization checks (CWE-862) on settings-update endpoints, meaning any internet-reachable WordPress installation running the affected plugin is exposed. No public exploit code or CISA KEV listing has been identified at time of analysis, but the unauthenticated, low-complexity attack vector makes this trivially exploitable by automated scanners.