Authentication Bypass
Monthly
Mitigation bypass in the Remote Settings Client component. This vulnerability was fixed in Firefox 156, Firefox ESR 115.41, Firefox ESR 140.16, and Firefox ESR 153.3.
Jpom through 2.11.12 exposes a broken object-level authorization flaw on the /build/branch-list endpoint, letting any authenticated user supply a repositoryId belonging to a different workspace and have the server resolve it without verifying ownership. This enables cross-workspace repository enumeration, disclosure of repository type, and execution of git ls-remote calls that reuse another workspace's stored Git credentials, leaking private repository metadata. Exploitation is low-complexity over the network with only a low-privileged account required, and publicly available exploit code exists, though the CVSS 4.0 base score is only 5.3 because the impact is limited to confidentiality.
Authenticated users of MISP 2.5.45 and earlier can list dashboard templates that are supposed to be restricted to other permission flags, such as perm_site_admin, because a MySQL type-juggling flaw makes the 'unrestricted' branch of the template query match every permission-restricted template. The bug is an incorrect-authorization error (CWE-863) in DashboardsController::listTemplates(), patched upstream in MISP 2.5.46; no public exploit code or CISA KEV entry was identified at time of analysis, and the CVSS 4.0 base score of 5.3 reflects only low confidentiality impact with no integrity or availability effect.
Unauthenticated access to the `/blacklist` endpoint of Maltrail (versions up to 3.0.1) allows any remote caller to retrieve source IP addresses of events that matched the operator's BLACKLIST rules, exposing internal network hosts flagged by the threat detection system. The oversight - a missing session check on one endpoint while all sibling endpoints (`/events`, `/counts`, `/hunt`, `/meta`, `/geo`) correctly required authentication - was confirmed by the vendor and patched in version 3.1 the same day it was reported. A public proof-of-concept exploit is available, making exploitation trivially scriptable against exposed instances.
Authorization bypass in subhajitkhan's online-clinic-management-system lets a remote, unauthenticated attacker take over an administrator session by manipulating the adminmail argument processed by session_start() in adminappview.php, with no password or token required. Publicly available exploit code exists and the maintainer has not responded to the issue report filed against the project, so no fixed release is available. With CVSS 4.0 base metrics of AV:N/AC:L/PR:N/UI:N and E:P, impact is scored low across confidentiality, integrity and availability, but the resulting admin session can expose patient and appointment records.
Improper access control in PHPGurukul Hostel Management System 3.0 allows an attacker to bypass authorization checks in the admin login handler /admin/includes/checklogin.php by manipulating the ID parameter, granting unauthorized access to administrative functionality. Exploitation is remotely reachable and publicly available exploit code exists (tracked via a GitHub PoC issue and VulDB entry), though the per-component impact is limited to low confidentiality, integrity and availability loss. EPSS/KEV signals are absent from the provided data, and the published CVSS 4.0 base metrics (AV:N/AC:L/PR:L/UI:N, all impacts Low) indicate a modest real-world risk rather than mass-exploitation potential.
Yao (YaoApp) through v1.0.0-rc22 allows any authenticated user to read complete team records via the GET /user/teams/:id endpoint, which authenticates the caller but never verifies team membership. Attackers who hold a low-privilege account and know or guess a team identifier can retrieve team name, description, owner information and settings. The flaw is remotely reachable with low complexity but yields only low confidentiality impact (CVSS 5.3), and no public exploit code or CISA KEV entry was identified at time of analysis.
Let me synthesize this into the required JSON. Key facts: - CVE-2026-91773, Soft Serve (charmbracelet/soft-serve), Git LFS lock metadata disclosure. - CWE-639 Authorization Bypass Through User-Controlled Key (IDOR) - CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N → 5.3 - Affected: 0.7.1 through 0.11.6 (fixed in 0.12.0) - Patch: vendor available; commit e34914699128c937afad167d43ccb5310e48b319 adds repo_id scoping. - No KEV, no POC noted explicitly. But commit includes tests. No EPSS given. - Tags: Authentication Bypass, Soft Serve. Product name: "Soft Serve" (charmbracelet soft-serve) — 2 words. Good. Prevalence: Soft Serve is a self-hosted Git server — niche. "low" or "rare". It's a fairly well-known project in the Charm ecosystem but not widely deployed enterprise. I'll say "low" with basis "self-hosted Git server, niche deployment footprint". Assessed CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N = 4.3. Wait: CVSS 3.1 with PR:L, C:L → base score. Let me compute: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Exploitability = 8.22 * AV(0.85) * AC(0.77) * PR(0.62) * UI(0.85) = 8.22*0.85=6.987; *0.77=5.38; *0.62=3.335; *0.85=2.835. Impact sub-score for C:L only: ISS = 1 - [(1-0.22)*(1-0)*(1-0)] = 0.22. Impact = 6.42*0.22 = 1.412. Base = roundup(min(1.412+2.835, 10)) = roundup(4.247) = 4.3. Fine. CVSS 4.0: matches provided: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Attack chain: Authenticate to Soft Serve → Access any repo with write permission (own repo) → Enumerate LFS lock IDs via lock list endpoint → Retrieve lock metadata from private repos → Recover file paths, usernames, timestamps. 5 steps. Exploitation conditions: requires authenticated account with write access to at least one repository; the LFS lock list endpoint accepts `id` query param; target must be using Soft Serve Git LFS locks feature with locks present in private repos. Limits: read-only (confidentiality only), no ability to modify/delete others' locks? Actually
Improper authentication in the admin Dashboard controller of PHPGurukul Blood Donor Management System 1.0 lets a remote, unauthenticated attacker reach administrative functionality by calling the controller's constructor route directly, bypassing the login/session check. Successful abuse exposes donor and blood-stock data and allows modification of records, giving low but real confidentiality, integrity and availability impact. Publicly available exploit code exists and the vendor has not published a fixed release, so every internet-facing deployment of version 1.0 should be assumed reachable by automated scanners.
Authenticated, low-privileged users of Webkul Bagisto 2.4.9 can obtain sensitive information belonging to other customers by manipulating object identifiers in the add-to-cart API and the downloadable-product fulfilment flow. The flaw is an insecure direct object reference (CWE-639) rated CVSS 6.5 with a network vector, low privileges, and confidentiality-only impact; no CISA KEV entry or public exploit code is associated with this CVE in the available data, so it is currently a patch-and-harden issue rather than an active-exploitation emergency.
Arista EOS network switches permit an authenticated 802.1X supplicant on an adjacent Layer 2 segment to send traffic unrestricted by its assigned ACL during a brief race window - spanning milliseconds to seconds - between the completion of the authentication handshake and the point at which the switch fully enforces the authorization policy. The flaw is classified under CWE-862 (Missing Authorization) and affects all EOS releases through 4.33.7.1M as well as specific 4.34.x and 4.35.x branches. No public exploit code has been identified and the issue is not listed in the CISA KEV catalog; its real-world impact is limited by adjacency requirement, authentication prerequisite, and the very short exploitation window.
HTTP CONNECT tunnel authentication bypass in goproxy through v15.3 permits unauthenticated remote clients to establish arbitrary TCP tunnels through a proxy that has basic authentication configured, completely nullifying the access control mechanism. Attackers send CONNECT requests without an Authorization header and the proxy accepts them unconditionally, enabling relay of arbitrary TCP traffic to otherwise-restricted destinations. No public exploit code or active exploitation has been identified at time of analysis, but the attack requires no credentials, no user interaction, and only basic HTTP client capability.
Arista EOS devices simultaneously running 802.1X port authentication and the RADIUS proxy feature with dynamic authorization can be manipulated by a low-privileged adjacent attacker to suppress RADIUS Change-of-Authorization (CoA) and Disconnect-Request messages targeting locally authenticated 802.1X sessions. By inducing a crafted RADIUS packet through a configured RADIUS proxy client interface, an attacker causes the switch to discard legitimate session-revocation orders from a RADIUS server or NAC system, allowing revoked endpoint sessions to persist on the network indefinitely. Arista discovered this issue internally and reports no known malicious exploitation in customer environments; no public exploit code exists at time of analysis.
IBM Sterling B2B Integrator (6.2.0.0 through 6.2.0.6_2, 6.2.1.0-6.2.1.2, 6.2.2.0-6.2.2.1) and IBM Sterling File Gateway Standard Edition in the same version ranges contain an improper authentication flaw (CWE-287) that lets a remote authenticated attacker bypass security restrictions. The CVSS 3.1 base score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N), indicating a low-privilege authenticated network attacker can gain limited read and modify capability without user interaction, but no confidentiality-integrity-availability loss beyond partial. There is no CISA KEV listing, no public exploit code identified, and no EPSS score supplied in the available intelligence, so this appears to be a targeted-patch issue rather than a mass-exploitation emergency.
IBM Sterling Secure Proxy versions 6.2.0.0 through 6.2.1.2 enforce authorization for certain administrative user interface components only on the client side, so an attacker who already holds a valid low-privileged account can cause the browser to render admin-only UI elements that should have been hidden. The result is a limited information disclosure (CVSS 4.3, C:L, no integrity or availability impact) rather than full administrative takeover, and no public exploit code or CISA KEV entry was identified in the supplied intelligence. Because the flaw is a missing server-side authorization check (CWE-285), any authenticated user of the affected deployment can probe it trivially with low attack complexity.
Apple macOS contains an improper access-control logic flaw in state management that allows a locally running app to read protected user data outside of its intended permission scope. The issue affects macOS Sequoia, macOS Tahoe and the macOS 27 (Golden Gate) line prior to the fixed releases, and is remediated in macOS Sequoia 15.8, macOS Tahoe 26.7 and macOS Golden Gate 27. The CVSS vector (AV:L/AC:L/PR:N/UI:R, C:H/I:N/A:N) shows this is a local, confidentiality-only issue requiring a user to launch or open the malicious app, with no public exploit identified at time of analysis and a low EPSS score of 0.18% (8th percentile) — real-world exploitation pressure is currently minimal.
Improper state management in Apple macOS (all versions prior to macOS 27 "Golden Gate") lets a locally installed application reach sensitive user data that normal macOS privacy and access controls are supposed to protect. The attack is local and needs the victim to launch the malicious app (AV:L, UI:R, PR:N), and the impact is confidentiality-only (C:H/I:N/A:N), which yields a moderate CVSS of 5.5. The issue is fixed in macOS 27 per Apple's advisory, EPSS is very low (0.14%, 3rd percentile), there is no CISA KEV listing, and no public exploit code has been identified.
Gatekeeper protection bypass in Apple macOS lets a locally executed, unprivileged application evade the operating system's notarization and quarantine checks, allowing unsigned or unnotarized code to run that Gatekeeper would normally block. The flaw is a logic/state-management error (CWE-693, protection mechanism failure) affecting macOS releases prior to macOS 27 (Golden Gate); exploitation requires the attacker to already possess a local foothold or to persuade a user into launching a malicious app, since the CVSS vector is AV:L/PR:L with no remote or unauthenticated path. Apple has shipped a vendor fix referenced in advisory 149035, EPSS is low at 0.16% (6th percentile), and no public exploit code or confirmed active exploitation has been identified at time of analysis - the real risk is as a chaining primitive to run code that Gatekeeper would otherwise reject.
A permissions-validation flaw (CWE-863) in Apple macOS versions prior to 27 (Golden Gate) and Xcode versions prior to 27 allows a locally installed app to reach user-sensitive data it should not be authorized to read. The issue is a local, confidentiality-only defect rated CVSS 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N): no privileges are needed, but the attack requires the victim to run the malicious application. Apple has released fixes in macOS 27 and Xcode 27; there is no CISA KEV listing, no public exploit code identified at time of analysis, and EPSS is very low at 0.16% (5th percentile), so real-world exploitation is unlikely to be widespread.
An improper access-control flaw in Apple macOS allows a locally running application to bypass authorization checks and read sensitive user data it should not be able to reach, with the fix delivered in macOS Sequoia 15.8 and macOS Golden Gate 27. Exploitation is local only and requires user interaction (the victim must launch the malicious or trojanized app), so the CVSS impact is limited to confidentiality (5.5 Medium). EPSS is negligible at 0.16% (5th percentile), there is no CISA KEV listing and no public exploit code identified at time of analysis, making this a routine update rather than an emergency patch.
Improper access control in Apple's Keychain service lets a locally installed app delete credentials stored by other applications on iOS 27, iPadOS 27, macOS Golden Gate 27, and visionOS 27 (all versions prior to these releases). The bug is fixed by removing the vulnerable code path; it is rated CVSS 5.5 with integrity-only impact, and there is no public exploit or CISA KEV confirmation at time of analysis (EPSS 0.15%).
Improper authorization checks in Apple's headphone motion data handling allow a locally installed app to read motion sensor data from connected headphones without prompting the user for consent, affecting iOS/iPadOS 26.7 and 27 and earlier, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27 and watchOS 27 and earlier. Exploitation requires a malicious or compromised app and user interaction, and the impact is limited to confidentiality of headphone sensor data (CVSS 5.5, C:H/I:N/A:N). Apple has shipped fixes in all affected operating systems; EPSS is low (0.20%, 10th percentile), there is no CISA KEV listing and no public exploit code identified at time of analysis.
An authorization flaw in Apple's operating systems lets a locally installed malicious app bypass Privacy preferences on affected iOS, iPadOS, and macOS builds. Apple addressed the issue through improved state management in iOS 18.7.10, iPadOS 18.7.10, iOS 27, iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.7.8, and macOS Sonoma 14.8.8. The CVSS 3.1 base score is 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N), EPSS is 0.21% (11th percentile), there is no CISA KEV listing and no public exploit code identified at the time of analysis.
Privacy preference bypass in Apple macOS allows a locally running application with normal (low) user privileges to circumvent the TCC consent controls that gate access to protected user data, affecting macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27. The attack surface is entirely local and non-network-facing: an attacker must first get an untrusted or malicious app installed and running on the device, after which no further user interaction is needed, and the resulting impact is capped at low confidentiality and low integrity with no availability loss and no privilege escalation or system compromise. Exploitation risk is low - EPSS is only 0.18% (8th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis - while vendor-released fixes are already available for all three affected release trains.
A locally installed application on macOS versions prior to macOS Golden Gate 27 can bypass Gatekeeper code-origin and notarization checks, weakening the platform control that is supposed to stop untrusted apps from launching. The flaw is assessed at CVSS 4.4 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N), meaning it requires local presence and normal user privileges, and the resulting impact is limited to partial confidentiality and integrity loss rather than code execution or denial of service. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing); EPSS is only 0.18% (8th percentile), and Apple has released a fix in macOS Golden Gate 27. Per the independent assessment, this is a genuinely low-priority issue despite the 'Authentication Bypass' tag.
Local information disclosure in Apple macOS before Golden Gate 27 allows an installed app to bypass system pasteboard sandbox restrictions and read sensitive pasteboard data, resulting in confidentiality impact only. The flaw is not remotely exploitable; it requires attacker-controlled code already running locally, typically a malicious or compromised app that the user has installed and launched. Apple fixed it in macOS Golden Gate 27, and no public exploit was identified at time of analysis (EPSS 0.17%, CVSS 5.5 Medium).
Incorrect authorization handling in Apple's iOS, iPadOS, macOS, and tvOS lets a locally installed app reach sensitive user data that should be fenced off by the platform's state and sandbox checks. The flaw is a local, low-privilege issue (CVSS 5.5, AV:L/PR:L) requiring a malicious or compromised app already running on the device — no network vector and no user interaction beyond launching the app. Apple has shipped fixes in iOS/iPadOS 26.7 and 27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, and tvOS 27; EPSS is very low (0.17%, 6th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis.
Local applications on macOS releases prior to Golden Gate 27 can bypass the Apple Intelligence security and consent prompts, evading the authorization gate that is supposed to require explicit approval before protected Apple Intelligence functionality is reached. Exploitation is not remote: an attacker must first get a malicious or abusable app onto the machine and running under normal user privileges (CVSS AV:L/PR:L, no user interaction at exploit time), and it is only meaningful where Apple Intelligence is present and enabled. The issue is a low-urgency local authorization flaw rather than an emergency - CVSS 5.5, EPSS 0.15% (5th percentile), no CISA KEV listing, and no public exploit identified at time of analysis - though Apple has addressed it with improved state management in macOS Golden Gate 27.
Improper access control in Apple iOS, iPadOS, and macOS lets a locally installed application running with low privileges read sensitive user data, with no user interaction required, affecting iOS and iPadOS before 26.7 and before 27 and macOS before Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. Apple fixed the authorization flaw (CWE-285) through improved access control as part of its 26.7/27 release cycle, so vendor patches are available for every affected platform. At a CVSS base score of 5.5 and an EPSS score of only 0.19% (9th percentile), this is a moderate-severity, low-priority local authorization issue; no public exploit code has been identified at time of analysis.
Archive expansion on Apple operating systems can slip past Gatekeeper's file-quarantine checks, allowing unsigned or un-notarized code inside a crafted archive to run without the normal block or warning prompt; macOS (Sequoia, Tahoe and Golden Gate), iOS/iPadOS, visionOS and watchOS are all affected and remediated in the 26.7/27 and 15.8 releases documented in Apple advisories 149034-149043. The flaw is local in nature (CVSS:3.1/AV:L/AC:L), requires the archive to actually reach and be expanded on the device, and carries bounded impact (C:L/I:L/A:N) because it defeats a trust warning rather than granting elevated execution - though the vendor's vector assumes low privileges and no user interaction while our independent assessment treats the expand/open step as user-driven. There is no public exploit identified at time of analysis and no CISA KEV listing, with EPSS at 0.18% (8th percentile), making this a genuinely low-priority issue despite the security-relevant nature of a Gatekeeper bypass; exploitation status is 'no public exploit identified at time of analysis'.
Improper access control in Apple macOS allows an application already running on the system to reach sensitive user data that should have been protected by a platform check, affecting macOS versions prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. The flaw is local-only and authenticated in the sense that it requires a malicious or compromised app executing with standard (non-root) user privileges (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 5.5) - there is no remote vector and no additional user interaction beyond launching the app, but confidentiality impact is rated High while integrity and availability are untouched. Apple does not disclose which specific protected resource or entitlement check is bypassed, so all pre-patch installs should be treated as affected. Risk is genuine but modest: EPSS is 0.17% (6th percentile), no public exploit code has been identified at time of analysis, and the vulnerability is not confirmed actively exploited (no CISA KEV listing); vendor patched versions are already available.
Improper authentication state management in Apple iOS and iPadOS versions prior to 27 lets someone with physical access to an already-unlocked iPhone or iPad view stored Wi-Fi passwords without supplying credentials. The flaw is purely physical (CVSS:3.1/AV:P/AC:L/PR:N/UI:N), carries a high confidentiality impact (C:H) but no integrity or availability effect, and does not affect devices running iOS 27 or iPadOS 27, where Apple corrected the state-handling logic. Exploitation is confirmed to be neither remotely reachable nor scalable, EPSS is only 0.21% (11th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis.
An improper authorization and state-management gap in Apple's Bluetooth stack lets a locally running app on affected macOS and watchOS builds reach Bluetooth device information it should not be able to read. Affected systems are macOS Golden Gate before 27, macOS Sequoia before 15.8, macOS Tahoe before 26.7, and watchOS before 27; the attacker must already have an app executing with app-level privileges (CVSS vector PR:L, with our assessment placing the attack vector as local rather than adjacent), so this is not an unauthenticated or remote path. Impact is confined to confidentiality of Bluetooth device data (C:L, no integrity or availability effect) and the issue is low severity overall - CVSS 3.5, EPSS 0.16% (6th percentile), no CISA KEV listing, and no public exploit identified at time of analysis.
Bypass of on-device network restrictions in Apple iOS/iPadOS, macOS Golden Gate, visionOS, and watchOS builds prior to version 27 allows a locally installed, already-running app to reach network resources the operating system should have blocked, producing low confidentiality and low integrity impact with no availability effect. Exploitation requires an app that is already installed and executing with normal, authenticated app privileges on the target device (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, score 4.4); there is no remote or unauthenticated attack path, no public exploit identified at time of analysis, and EPSS is a low 0.21% (11th percentile). Apple has shipped vendor-released fixes in iOS 27, iPadOS 27, macOS Golden Gate 27, visionOS 27, and watchOS 27.
Gatekeeper enforcement in Apple macOS can be bypassed by a malicious application that is delivered locally and opened by the user, letting the app run without satisfying macOS's normal code-signing and notarization checks. The flaw is a logic error (CWE-693, protection mechanism failure) affecting macOS builds prior to Golden Gate 27, Sequoia 15.8, Tahoe 26.6 and Tahoe 26.7; CVSS 5.5 reflects an integrity-only, non-privileged local impact that requires user interaction and grants no direct privilege escalation or confidentiality loss. No public exploit code has been identified at time of analysis and EPSS is low at 0.21% (11th percentile), so the practical value of the bug is as a stage in a broader malware delivery chain rather than a standalone compromise.
Apps already running on macOS versions prior to Golden Gate 27 can modify Privacy (TCC) preferences they are not authorized to change, letting a malicious app grant itself access to consent-gated resources such as the camera, microphone, or other protected data without ever prompting the user. The root cause is an incorrect-authorization weakness (CWE-863) that Apple addressed by adding restrictions to the permission check, so exploitation is not remote: the attacker must first deliver and run code on the host (AV:L, PR:L, UI:N), making this primarily a post-compromise, integrity-only escalation of an app's privacy privileges (C:N/I:H/A:N). EPSS is only 0.17% (7th percentile), there is no CISA KEV entry and no public exploit identified at time of analysis, and a vendor-released fix exists in macOS Golden Gate 27.
Local applications running on unpatched Apple macOS builds can bypass permission checks and read sensitive user data they are not authorized to access. The issue affects macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27, and was resolved through improved permissions validation in those releases. No public exploit code has been identified at time of analysis and the EPSS score is negligible (0.16%, 6th percentile), making this a genuine but low-priority, confidentiality-only local flaw.
Gatekeeper code-signing enforcement in Apple macOS can be bypassed by an app that is already present and running on the host, allowing it to launch untrusted code that macOS would normally block. The affected software is macOS prior to the fixed builds (Sequoia before 15.8, Tahoe before 26.7, and the next-generation release line before 27), and the CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N describes a local attack requiring an attacker to have already achieved normal user-level execution, with low confidentiality and integrity impact and no availability impact. No public exploit has been identified at time of analysis and there is no CISA KEV listing; EPSS is 0.21% (11th percentile), consistent with a low-to-moderate, locally-scoped issue rather than an urgent priority.
Improper permission checks in macOS snapshot handling allow a locally installed app to read protected user data, an issue Apple resolved with stronger permissions logic in macOS Golden Gate 27. The flaw is a local access-control problem (CWE-284) that requires user interaction but no special privileges (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, base score 5.5), and it carries a low EPSS of 0.19% (9th percentile). No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, so this is best treated as a moderate-severity confidentiality issue rather than an urgent priority.
Holding a locked iPhone or iPad, an attacker can reach a lockscreen-accessible interface that improperly passes an authentication check, allowing sensitive user information to be viewed without the passcode being entered. The flaw is a logic error classed as CWE-287 (improper authentication) that affects iOS and iPadOS builds prior to 26.7 and 27, and Apple has shipped fixes in iOS/iPadOS 26.7 and iOS/iPadOS 27, so it is fully remediated by updating. Exploitation requires hands-on physical possession of the locked device and cannot be performed remotely or at scale; EPSS is 0.17% (6th percentile) and no public exploit has been identified at time of analysis, making this a low-to-medium real-world priority driven mostly by confidentiality exposure on lost or stolen devices.
Unauthorized local network access on Apple macOS (all releases prior to Golden Gate 27) lets a malicious or compromised application communicate with local network devices without triggering the macOS Local Network consent prompt. The root cause is improper permission state management (CWE-284), and exploitation is strictly local: the user must launch the offending app (CVSS UI:R), with no remote or unauthenticated path. The independent assessment downgrades confidentiality impact to Low relative to the published CVSS 5.5, limiting practical consequences to reconnaissance of LAN-adjacent devices; no public exploit code has been identified and EPSS is only 0.14% (4th percentile), consistent with a low-priority, targeted issue. Apple has fixed the flaw in macOS Golden Gate 27.
Sensitive user data disclosure in Apple iOS and related platforms allows a locally installed malicious app to bypass entitlement checks and access protected data, affecting Safari before 27, iOS/iPadOS before 26.7 and 27, macOS before Golden Gate 27, and visionOS before 27. The flaw requires local app installation and user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R) and only impacts confidentiality (C:H) with no integrity or availability effect. No public exploit has been identified at time of analysis, and EPSS is 0.18% (7th percentile), indicating low exploitation likelihood.
A sandboxed application running on Apple iOS/iPadOS, macOS Golden Gate, tvOS, visionOS, or watchOS can bypass authorization checks and read contents of the System Keychain, exposing stored secrets such as credentials, certificates, and tokens. The flaw stems from incorrect authorization combined with faulty state management (CWE-863) and affects all versions prior to the 27 release train; the platform owner has shipped fixes in iOS 27, iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27, and watchOS 27. The CVSS v3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, score 5.5) is consistent with our independent assessment: this is a genuine but locally-scoped access-control defect that requires an attacker to get a sandboxed app onto the device and have the user launch it (UI:R), so it cannot be triggered remotely over the network. EPSS is 0.16% (6th percentile) and no public exploit code has been identified at time of analysis, with no CISA KEV listing - impact is limited to confidentiality (keychain disclosure) with no integrity or availability effect, and patched 27-or-newer systems are not exposed.
Authorization bypass in Apple macOS allows a locally-running app to read sensitive user data without the user's consent, affecting macOS versions below Sequoia 15.8, below Tahoe 26.7, and below Golden Gate 27. Exploitation requires an attacker to first get a malicious or compromised application onto the machine and running under a standard, non-administrative user account (CVSS 3.1 AV:L/PR:L/UI:N), so this is not remotely reachable and no user interaction is needed once that app executes. Impact is limited to confidentiality of user data (C:H, I:N, A:N) - there is no code execution, privilege escalation, or system modification, and the EPSS score of 0.17% (6th percentile) plus the absence of KEV listing indicate no public exploit identified at time of analysis; Apple has released patched builds.
Gatekeeper protection in Apple macOS can be bypassed by a malicious application, allowing unsigned or unnotarized code to launch on unpatched Macs. The flaw is a state-management logic error in the Gatekeeper check, rated CVSS 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N): exploitation is local and requires the victim to download and open an attacker-controlled app, so it depends on user interaction rather than a remote network path, and it yields no confidentiality or availability impact by itself - it must be chained with a malicious payload. Affected systems are macOS versions below Golden Gate 27, Sequoia 15.8, and Tahoe 26.7; there is no public exploit identified at time of analysis, EPSS is low at 0.18% (8th percentile), and no CISA KEV entry exists.
An incorrect authorization check in Apple macOS lets an application already running on a Mac read sensitive user data it should not be able to reach, an impact limited to confidentiality with no code execution, modification, or denial of service. Exploitation requires local code execution on the target (the assessed vector is AV:L/PR:L/UI:N), so it is only reachable by a malicious or attacker-controlled app already present on the device, and only on unpatched systems below macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. Apple has released fixes in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27; no public exploit code or confirmed active exploitation has been identified, and EPSS is low at 0.19% (9th percentile), making this a moderate, locally-scoped risk rather than an urgent priority.
Improper access control in Apple iOS and iPadOS, macOS Tahoe, and visionOS lets a locally installed app read user-sensitive data that it should not be able to reach. The flaw (CWE-284) stems from insufficient validation checks and is remediated in iOS/iPadOS 26.6, macOS Tahoe 26.6, and visionOS 26.6; the assessed vector (CVSS 5.5, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) means exploitation requires the victim to install and launch a malicious app on an unpatched build, with no remote attack path and no integrity or availability impact. The attacker's app needs no special privileges, but there is no public exploit identified at time of analysis and EPSS is low at 0.19% (9th percentile), so this is a genuine but low-priority confidentiality issue.
Improper access control (CWE-284) in Apple iOS, iPadOS, and macOS allows a locally installed app to read user-sensitive data outside the permission boundary the operating system is supposed to enforce, an information-disclosure impact rated CVSS 5.5 (confidentiality High, integrity None, availability None). Exploitation is local and requires user interaction: the attacker must first get a malicious or compromised app onto the device and convince the user to launch it (AV:L, PR:N, UI:R), so there is no remote, network-triggerable, or self-propagating path. Apple has released fixes in iOS 26.7, iPadOS 26.7, iOS 27, iPadOS 27, macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27; no public exploit code has been identified at time of analysis and EPSS is low at 0.17 percent (7th percentile), with no CISA KEV listing.
Persistent device identifier disclosure in Apple iOS, iPadOS, macOS, tvOS, visionOS and watchOS stems from an incorrect authorization check that lets an ordinary, unprivileged installed app read identifiers it should not be able to access (CWE-863, CVSS 5.5, C:H/I:N/A:N). Exploitation is local-only (AV:L, PR:N) and requires user interaction to install and launch a malicious or compromised application on a device running an unpatched OS; there is no remote or network path, and no public exploit code has been identified at time of analysis, with EPSS at 0.17% (7th percentile) and no CISA KEV listing. Apple has released fixed versions and the impact is confined to confidentiality/privacy rather than code execution or data modification.
Improper access control in Apple's operating system family (iOS/iPadOS, macOS, tvOS, visionOS, watchOS) lets a locally installed app bypass intended permission restrictions and read sensitive user data it should not be able to reach. Apple addressed the flaw with additional restrictions in iOS 26.7/iPadOS 26.7, iOS 27/iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27, and watchOS 27. Exploitation requires the attacker to already run code on the device as an app (PR:L, AV:L), and no public exploit code or active exploitation has been identified; EPSS is only 0.20% (10th percentile) and CISA SSVC records exploitation as 'none'.
An improper authorization flaw in Apple iOS/iPadOS and macOS Tahoe allows a locally installed application to reach sensitive user data that the platform's authorization state checks should have blocked. Apple addressed the flaw through improved state management, shipping fixes in iOS 26.6, iPadOS 26.6, and macOS Tahoe 26.6 for all versions prior to those releases. The issue is local-only (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, 5.5) with confidentiality impact only; EPSS is 0.15% (5th percentile), CISA SSVC rates exploitation as 'none' and technical impact as 'partial', and no public exploit code was identified at time of analysis.
An incorrect-authorization flaw in Apple's Bluetooth state management allows an already-installed app to obtain Bluetooth access it was never granted, undermining the platform's per-app permission model on iOS 27, iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27 - but only on versions prior to those releases. Apple fixed the issue through improved state handling and published coordinated advisories for every affected platform; a local attacker or malicious app is required, so this is not remotely reachable without code execution already on the device. No public exploit code has been identified and EPSS is very low (0.20%, 10th percentile), so this rates as a patching-hygiene item rather than an emergency.
Missing authorization in the A2A Java SDK (a2aproject/a2a-java) 1.2.0 allows a caller with a valid account to invoke the ListTasks operation without the list-scoped read check that guards other task operations, so task listings are returned to principals that the configured TaskAuthorizationProvider may have intended to reject entirely. The flaw lives in AuthorizationRequestHandlerDecorator.onListTasks in server-common, which delegated to the handler without first consulting the authorization provider for the list scope, leaving protection to per-task filtering inside the TaskStore. It is fixed in release 1.3.0 (tag v1.3.0.Final, commit e9a1abf9c90c02b16d17293afdc3cc2f555d63a6); CVSS 4.0 base is 5.3, there is no CISA KEV listing and no public exploit code identified at time of analysis.
An authentication bypass in IBM WebSphere Application Server 9.0 and 8.5 allows an attacker on an adjacent network segment to reach and invoke an administrative console servlet without valid credentials, because the servlet is missing the authorization check that should gate it (CWE-862). Successful exploitation gives low-level confidentiality and integrity exposure plus a high availability impact on the affected server. IBM has released a vendor patch, and there is no CISA KEV listing, no publicly available exploit code, and no EPSS signal in the supplied data, so the practical risk is concentrated in environments where the admin console is reachable from an untrusted adjacent network.
Authentication bypass in IBM WebSphere Application Server 8.5 and 9.0 allows an unauthenticated attacker positioned on an adjacent network segment to reach request-handling functionality that performs no authorization check (CWE-862) and read sensitive information from the response. IBM has released a vendor patch, and there is no public exploit code or CISA KEV entry associated with this issue at time of analysis, so exploitation is not confirmed actively exploited. CVSS rates it 6.5 with confidentiality-only impact and PR:N/UI:N, but no EPSS score was supplied, leaving real-world exploitation likelihood unquantified.
Authorization bypass in IBM WebSphere Application Server 8.5 and 9.0 lets an attacker positioned on an adjacent network segment reach functionality without the required authorization checks, resulting in limited (low) confidentiality exposure with no integrity or availability impact. The published CVSS 3.1 score is only 3.1 (AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N), reflecting that exploitation demands network adjacency and a high-complexity precondition rather than an internet-facing attack. There is no CISA KEV listing, no public exploit code identified in the provided sources, and an EPSS score was not supplied; IBM has published a fix. Note the tension between the 'authorization bypass' label and the very low scored impact — the advisory's own severity framing should be verified directly against the IBM support page.
An authentication bypass in IBM WebSphere Application Server 8.5 and 9.0 allows remote attackers to reach protected resources without valid credentials when the XD or Intelligent-Management features are in use. Successful exploitation yields unauthorized access to confidential data (C:H) with no direct integrity or availability impact, consistent with the CWE-650 (trusting HTTP permission methods) classification. IBM has published an advisory and patch (node/7286610); no public exploit code or CISA KEV listing was present in the supplied intelligence, so active exploitation is unconfirmed.
An improper authentication flaw (CWE-287) in IBM Langflow OSS versions 1.0.0 through 1.10.2 lets a remote attacker who already holds a valid low-privileged account change the password of another user's account, resulting in account takeover rather than direct code execution. The CVSS 3.1 score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L), reflecting that exploitation requires an authenticated session and primarily damages integrity and availability of the targeted account. No public exploit code has been identified and the issue is not listed in CISA KEV, but SSVC flags partial technical impact and the vendor has published a fix; the exact patched version string is not enumerated in the available data.
IBM i Navigator for i — the browser-based administration console shipped with IBM i 7.3, 7.4, 7.5 and 7.6 — can be made to ignore the binding that ties an administrative session to the client's source IP address, allowing a remote, unauthenticated attacker (CVSS PR:N/UI:N) to reach sensitive information that should have been confined to a legitimate session. IBM scores the exposure 5.3 with confidentiality-only impact (C:L/I:N/A:N), consistent with a targeted information disclosure rather than a full compromise of the host. Vendor fixes are published, and no public exploit code or CISA KEV entry appears in the supplied intelligence, so this is best treated as a patch-on-schedule hardening item rather than an emergency.
Really Simple Security (formerly Really Simple SSL) before 9.8.2 ships an unguarded profile-page update handler that lets an authenticated low-privileged WordPress user bypass mandatory two-factor authentication indefinitely. By POSTing to the profile update endpoint without the two-factor-authentication field, the attacker skips nonce verification and reaches delete_two_fa_meta(), which resets the grace-period anchor timestamp on every login cycle, so enforced 2FA is perpetually deferred rather than satisfied. The flaw is rated low severity (CVSS 4.0 base 2.3, PR:L, VI:L) and no public exploit code or CISA KEV entry was identified at time of analysis; a vendor patch is available in 9.8.2.
Missing authorization in the Django-CRM bulk case update endpoint (backend/cases/bulk_views.py) allows any authenticated member of an organization to edit, reassign, or close cases belonging to other users. Affected releases are django-crm 1.0 through 1.2; the same code path also skips the model's close-transition validation, so a case can be closed without the recorded approval that the single-case workflow requires. Version 1.3.0 resolves the issue (patch commit 799bb121), CVSS 4.0 rates it 5.3 (AV:N/AC:L/PR:L/UI:N), SSVC records no exploitation and no automatable vector, and no public exploit code has been identified at time of analysis.
Let me synthesize. Product: Siglet / Eclipse Data Plane Core. The description mentions "Siglet" refresh token handler, CPE says eclipse_data_plane_core. Primary product name — 1-3 words. Probably "Eclipse Data Plane Core" or "Siglet". Let me pick "Siglet" — hmm, the CPE is Eclipse Data Plane Core. The description says "In Siglet current and past versions". Siglet appears to be a component within Eclipse Data Plane Core (Eclipse Dataspace Components). Tags list Eclipse Data Plane Core. I'll use "Eclipse Data Plane Core" as primary? The rules say pick primary product. The CPE is the authoritative affected product. But description says Siglet. Hmm. I'll say "Siglet" — actually product_name 1-3 words only. Let me choose "Eclipse Data Plane Core" (4 words? Eclipse, Data, Plane, Core = 4 words). That violates 1-3 words. "Siglet" is 1 word. I'll go with "Siglet". Hmm, but the affected products refer to Eclipse Data Plane Core. Perhaps Siglet is the SSI/token component. I'll use "Siglet" as product name and mention Eclipse Data Plane Core in affected_products. Actually, to be safe, maybe "Eclipse Data Plane Core" — 4 words is over. Let's use "Siglet". CVSS 6.3, vector CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N — network, high complexity, no privileges, no UI, low impact on C/I/A. CWE-290: Authentication Bypass by Spoofing. Issue: refresh token handler does not enforce proof of possession of the issuer DID. So an attacker who obtains a refresh token (or can present a refresh token) without proving possession of the private key corresponding to the issuer DID can redeem it — token theft/replay allows issuing new access tokens. That's authentication bypass by spoofing: the token handler accepts a refresh token without verifying the DID key binding. Affected versions: Eclipse Data Plane Core 0.1.0 ≤ 0.1.3 and commit range a6f7d4cc... < 882fe22d... Patch: Available from vendor. The commit 882fe22db42bc67abfd0304c4cdb141b762c35d1 is likely the fix com
An attribute-read sandbox bypass in the PraisonAI multi-agent framework (pip package praisonaiagents before 1.6.59) lets prompt-influenced Python code reach blocklisted dunder attributes such as __class__, __bases__, __globals__ and __dict__, exposing in-process objects and secrets to the attacker. Exploitation requires the execute_code tool's sandbox mode with approval automatically granted (for example via PRAISONAI_AUTO_APPROVE or the YAML auto-approval path), after which two CPython semantics are chained: runtime string assembly evades the AST blocklist and str.format/str.format_map resolve dotted fields through C-level attribute access that never consults the Python-level _safe_getattr wrapper. The result is a high-confidentiality read primitive rather than a complete in-process execution chain; the vendor has published a fixed release (1.6.59) plus a public GitHub advisory containing a reproducer, and there is no CISA KEV listing indicating active exploitation.
PraisonAI's Server-Sent Events (SSE) server accepts /publish, /events, and /info requests without ever checking the ServerConfig.auth_token value, so any client that can reach the listening port can broadcast arbitrary events into every connected client's stream and read back server configuration and connected-client counts. Affected are praisonaiagents releases prior to 1.6.58 (some package metadata lists 1.6.59 as the fixed version); the npm-style pip package is the delivery vehicle and the flaw only manifests when the optional SSE server mode is started. Public proof-of-concept curl commands are published in the GitHub advisory (GHSA-35w5-pcw4-jx94), but there is no CISA KEV listing and no confirmed active exploitation; CVSS 4.3 with an adjacent-network vector reflects a real but bounded integrity/confidentiality problem rather than remote code execution.
Cache invalidation in novel-plus through 5.3.3 exposes an unauthenticated HTTP endpoint protected only by a hardcoded default password embedded in the application's source-controlled configuration file, allowing any remote attacker who supplies the known default value in the URL path to forcibly invalidate portal caches at will. The root cause (CWE-1392: Use of Default Credentials) means the credential is fully disclosed in the public GitHub repository and a VulnCheck-reported Python POC, reducing exploitation to a trivial one-liner. No vendor-released patch exists as of the latest tagged release v5.3.3, leaving all deployments that have not manually rotated the credential exposed with a publicly available exploit.
Unauthenticated CAPTCHA bypass in SP Page Builder Pro (Joomla extension, versions 5.1.4-6.9.0) allows any remote attacker to defeat form bot-protection by supplying attacker-controlled CAPTCHA parameters directly in the HTTP request. The optin_form addon reads the CAPTCHA type, expected answer, and enabled flag from user-supplied request data instead of the server-stored configuration, reducing verification to a trivially solvable md5($captcha_question) == $captcha_answer check where the attacker supplies both operands. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though SSVC classifies it as automatable, making large-scale scripted abuse realistic.
CAPTCHA verification in SP Page Builder Pro's Contact, Opt-in, and Form Builder addons can be defeated on any Joomla site running versions 3.2.6 through 6.9.0 by submitting the parameter view_type=module alongside any non-empty token string. The addon silently discards the CAPTCHA plugin's actual onCheckAnswer verification result and substitutes a trivially-satisfied non-empty-string check whenever this attacker-controlled parameter is present, rendering all configured CAPTCHA types ineffective for forms placed inside SP Page Builder modules. No public exploit has been identified at time of analysis, but the bypass is trivially automatable per SSVC assessment, requiring only a single parameter change in a standard form POST.
Board-creation permission enforcement is absent from three Mattermost Boards API endpoints-board duplicate, boards-and-blocks, and archive-import-allowing any authenticated user who has been denied board-creation rights to circumvent that restriction and create boards in the workspace. Affected are Mattermost versions 11.9.0, 11.8.x through 11.8.4, 11.7.x through 11.7.7, and 10.11.x through 10.11.22, as confirmed by advisory MMSA-2026-00715. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog; real-world impact is limited to unauthorized board creation with no confidentiality or availability consequence.
Incorrect authorization enforcement in Apache Doris lets any authenticated user read data they were never granted privileges to access, breaking tenant and role isolation in the MPP database. The flaw affects the 2.0.x–2.1.x, 3.0.x, 4.0.0–4.0.7 and 4.1.0–4.1.3 lines, is remotely reachable by any low-privileged account without user interaction, and is rated CVSS 6.5 with confidentiality-only impact. Apache has published fixed releases 4.0.8 and 4.1.4; no public exploit code and no confirmed active exploitation were identified in the available intelligence.
Unauthenticated REST API access on Contec's CPSN-MCB271 series Remote I/O Coupler Unit (Server Type) allows any network-reachable attacker to read industrial I/O sensor values and issue output control commands without credentials. The vulnerability arises from a complete absence of authentication on the device's REST interface, exposing physical process control functions directly over the network. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS 4.0 base score of 6.9 (AV:N/AC:L/AT:N/PR:N/UI:N) reflects a straightforward, condition-free exploitation path.
Missing authentication on the API Command Endpoint in 0x4m4's HexStrike AI (hexstrike_server.py) allows any remote, unauthenticated caller to invoke server-side API commands without presenting credentials. All commits through d689933ff579 in the hexstrike-ai repository are affected; the project uses rolling releases with no discrete versioning, and the maintainer has not responded to the responsible disclosure filed in GitHub issue #223. A public exploit has been disclosed (CVSS 4.0 E:P), lowering the bar for exploitation to any HTTP client with network reach to the exposed server.
Cross-tenant SMTP sender spoofing in N-able Mail Assure (all versions through April 2026) permits any authenticated tenant to specify arbitrary MAIL FROM envelope addresses - including domains belonging to other co-hosted tenants - without the relay enforcing any domain-to-account ownership binding. Because the shared relay is itself listed in the SPF records and DMARC policy of every hosted tenant domain, spoofed outbound messages pass SPF and DMARC validation at recipient mail servers, giving the attack the appearance of fully authorized email. N-able has publicly stated this is intended behavior of its shared relay architecture, making no vendor patch expected. A researcher demonstration gist has been published, and no public exploit or CISA KEV listing exists at time of analysis.
Unauthenticated file upload in Anil-matcha Open-Generative-AI (versions up to 1.0.11/2.0.0) allows any remote attacker to upload arbitrary files - including HTML, SVG, and executable types - to the application's S3 backend via the /api/upload-binary proxy endpoint. The endpoint accepted requests without any API key check and imposed no restrictions on file type or content, as confirmed by the patch commit f013270957f. No active exploitation or public proof-of-concept has been identified at time of analysis; EPSS data was not provided.
The graphiti FastAPI-based graph memory REST API (getzep/graphiti ≤ 0.30.2) shipped its ingest and retrieve routers with zero authentication - no API key, no token, no session check of any kind. Any unauthenticated remote caller with network access to the service can read stored knowledge-graph episodes or inject and overwrite graph data by sending ordinary HTTP requests. No public exploit code has been identified, but the barrier to exploitation is effectively zero: the attack requires only HTTP client access and knowledge of endpoint paths. No KEV listing at time of analysis.
Authentication bypass in Cheshire Cat AI up to version 1.9.2 allows remote unauthenticated attackers to manipulate the `user_id` argument within the `_authorize_http_key` function to circumvent HTTP API key validation entirely. Any publicly exposed Cheshire Cat AI instance is at risk of unauthorized access to its AI agent API, enabling arbitrary interaction with the agent without valid credentials. A proof-of-concept exploit has been publicly disclosed via GitHub issue #1137, and the project maintainers had not responded to the disclosure at time of writing; no patch is available.
Privilege escalation through parameter manipulation in Rizwan17's inventory-management-system allows remote unauthenticated attackers to register accounts with arbitrary privilege levels, including administrative roles, by supplying a crafted `usertype` value to the `createUserAccount` function in `register.php`. The vulnerability stems from the registration handler trusting client-controlled role values without server-side enforcement of permitted self-registration tiers. A public exploit is available via a GitHub issue report, and the vendor has not responded to the coordinated disclosure as of the time of reporting.
Improper access control in Rizwan17's PHP-based inventory-management-system exposes dashboard.php to unauthorized access via manipulation of the `userid` parameter, allowing remote unauthenticated attackers to access other users' data or bypass authentication controls. The affected codebase is identified by commit bfe78a330d01bb26b9daec5dc9ecd5c77900e03f and is distributed as a rolling release with no versioned patch available. A public proof-of-concept exploit has been published in a GitHub issue, and the maintainer has not responded to the responsible disclosure.
Authorization bypass in Apache Storm Logviewer 3.0.0 exposes daemon logs and tenant log file listings to any filter-authenticated user, entirely disregarding the configured `logs.users` and `logs.groups` access controls. A boolean short-circuit in the daemon log authorization path discards the authorizer's decision whenever the daemon-log flag is set, and the daemon log page and download endpoints are reached without consulting an authorizer at all; additionally, the listing endpoints `/listLogs` and `/searchLogs` accept a user argument but never apply it. On a multi-tenant Storm cluster, any user who passes the servlet filter can read nimbus.log, supervisor.log, and other daemon logs-which contain co-tenant topology names, job owners, and configuration fragments-and enumerate all worker log file names. No public exploit identified at time of analysis.
Missing authentication on update endpoints in jaychouchannel's Tourism-Management-System exposes write operations across 12 Spring controllers - including chat messages, forum posts, hotel/restaurant discussions, news, friend links, and bookmarks - to unauthenticated remote attackers. The root cause is confirmed by the patch commit (84d8ec3): the custom `@IgnoreAuth` annotation was incorrectly applied to update-path handlers, causing the authentication interceptor to skip those routes entirely. A public proof-of-concept exists via GitHub Issue #11; no CISA KEV listing has been issued.
Unauthenticated access to the AWS API Gateway endpoint in simalexan/api-lambda-send-email-ses allows any remote attacker to invoke the SES.sendEmail Lambda function without credentials, abusing the deployer's AWS Simple Email Service account to send arbitrary emails. Affected deployments are those built from any commit up to bda6869aa81371d1e872242e74fe7d953edb818d, with no patched release available as the project uses rolling delivery and the maintainer has not responded to the disclosure. No public exploit code or CISA KEV listing exists, but exploitation requires only knowledge of the deployed API Gateway URL and a simple HTTP request.
Hard-coded API token in dromara orion-visor through version 2.5.7 allows remote unauthenticated attackers to bypass the ExposeApi authentication gate enforced by ExposeApiAspect.beforeExposeApi. The static token is now publicly documented in a proof-of-concept writeup on GitHub after the vendor failed to respond to the responsible-disclosure issue report. No public exploit confirmed in CISA KEV at time of analysis, but a POC is available, materially lowering the bar for exploitation.
Improper access control in WARP-Clash-API (vvbbnn00) allows remote attackers to bypass key-based authorization in the Surge subscription handler, gaining unauthorized read and write access to subscription data. The affected function is get_surge_subscription in services/subscription.py, where manipulation of the key argument circumvents access control checks. A public proof-of-concept exploit exists on GitHub, and the product is abandoned with no upstream fix available or anticipated.
Authentication bypass in vvbbnn00's WARP-Clash-API allows unauthenticated remote attackers to circumvent the `authorized` function by manipulating the SECRET_KEY argument, gaining unauthorized access to the API's proxy configuration management functions. All versions up to commit c7bf2360073959861219b422e51ae86411051b46 are affected, and no patch exists because the maintainer has abandoned the project and did not respond to disclosure. A public proof-of-concept exploit is available via a GitHub gist, lowering the bar for exploitation against any internet-exposed instance.
Missing authentication in WWBN AVideo's Live plugin allows unauthenticated remote attackers to inject arbitrary socket notification messages to any administrator whose live stream key is known. The endpoint `/plugin/Live/socketMessageLiveOwner.json.php` validates that the stream *owner* holds admin privileges but performs no caller authentication (`User::isLogged()` is never invoked) and enforces no CSRF token, meaning the caller-identity check is entirely absent. No patch was available at time of publication; VulnCheck reported the issue against commit c3edcc274c389816d434acadac07ee78eaf330c1 and earlier.
Unauthenticated information disclosure in WWBN AVideo through commit c3edcc274c exposes inactive admin menu items and embedded secret query parameters via the unprotected `plugin/TopMenu/menuItems.json.php` PHP endpoint. Any network-reachable attacker can POST a `menuId` parameter to retrieve admin-tool URLs that are hidden from the public navbar, including secret tokens or keys embedded directly in those URLs. While the direct impact is limited confidentiality exposure (CVSS 4.0 VC:L), the leaked secret query parameters represent a stepping stone that could enable follow-on attacks against otherwise-obscured admin functionality. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated API abuse in the WPBot WordPress plugin before 8.5.7 allows any remote attacker to invoke the plugin's AI provider relay endpoints without credentials or a nonce, causing the site's configured third-party API keys (e.g., OpenAI) to issue requests and accrue charges on the site owner's account. The root cause is a complete absence of WordPress capability checks and nonce verification on multiple `wp_ajax_nopriv`-eligible AJAX actions. No public exploit code or CISA KEV listing exists at time of analysis; vendor-released patch 8.5.7 is confirmed available.
Improper certificate validation (CWE-295) in an ICS component's reverse proxy allows a network-adjacent attacker to impersonate the identity provider during token discovery, introspection, and credential exchange, resulting in forged authentication tokens being accepted across the deployment. The affected product is covered under ICS-CERT advisory ICSA-26-254-01, indicating an industrial or operational technology context. No public exploit code or active exploitation has been identified at time of analysis; exploitation requires adversarial positioning on the internal network segment between the reverse proxy and the identity provider.
Reverse proxy authentication passthrough in an ICS inventory-management component exposes the bundled credential-store administrative interface directly to the network when a specific authentication mode is configured. Under this mode, the gateway forwards requests to the credential store's admin UI without enforcing its own authentication, delegating all access control to that third-party interface's own login mechanism. This is the same OT product covered by CISA advisory icsa-26-254-01, which also documents CVE-2026-90456 (default credentials in example config); if both conditions align, an attacker can reach the admin UI of the credential store that gates every other service in the deployment with no gateway-layer resistance.
OCI artifact signature verification bypass in Doco-CD prior to v0.90.1 allows an attacker with write access to a monitored OCI registry tag to circumvent the global OCI_TRUST_POLICY enforcement and deploy unsigned or improperly signed artifacts. By publishing an artifact containing a crafted .doco-cd.yml with oci.verify: false, the attacker exploits a circular trust dependency - the tool reads per-deployment config from artifact contents before verifying that artifact - causing signature checking to be disabled for that same artifact. The vendor-released patch at v0.90.1 enforces a strict no-downgrade trust boundary; no public exploit has been identified at time of analysis.
In the Linux kernel, the following vulnerability has been resolved: svcrdma: Use svc_xprt_put to free listener on create failure svc_rdma_create() calls kfree(cma_xprt) when svc_rdma_create_listen_id() fails. svc_xprt_init() has already acquired a net namespace reference via get_net_track(); kfree bypasses svc_xprt_free() which releases it. Replace the kfree() with svc_xprt_put() so the kref_init birth reference drops to zero and svc_xprt_free() dispatches svc_rdma_free() to clean up properly. sc_cm_id is still NULL at that point; the preceding patch added the necessary NULL guard in svc_rdma_free(). svc_xprt_free() also drops the module reference via module_put(), but the caller _svc_xprt_create() does the same on xpo_create failure, double-putting the single try_module_get() it acquired. Take a compensating __module_get() before the svc_xprt_put() to keep the count balanced, matching the convention in svc_rdma_accept()'s error path.
Mitigation bypass in the Remote Settings Client component. This vulnerability was fixed in Firefox 156, Firefox ESR 115.41, Firefox ESR 140.16, and Firefox ESR 153.3.
Jpom through 2.11.12 exposes a broken object-level authorization flaw on the /build/branch-list endpoint, letting any authenticated user supply a repositoryId belonging to a different workspace and have the server resolve it without verifying ownership. This enables cross-workspace repository enumeration, disclosure of repository type, and execution of git ls-remote calls that reuse another workspace's stored Git credentials, leaking private repository metadata. Exploitation is low-complexity over the network with only a low-privileged account required, and publicly available exploit code exists, though the CVSS 4.0 base score is only 5.3 because the impact is limited to confidentiality.
Authenticated users of MISP 2.5.45 and earlier can list dashboard templates that are supposed to be restricted to other permission flags, such as perm_site_admin, because a MySQL type-juggling flaw makes the 'unrestricted' branch of the template query match every permission-restricted template. The bug is an incorrect-authorization error (CWE-863) in DashboardsController::listTemplates(), patched upstream in MISP 2.5.46; no public exploit code or CISA KEV entry was identified at time of analysis, and the CVSS 4.0 base score of 5.3 reflects only low confidentiality impact with no integrity or availability effect.
Unauthenticated access to the `/blacklist` endpoint of Maltrail (versions up to 3.0.1) allows any remote caller to retrieve source IP addresses of events that matched the operator's BLACKLIST rules, exposing internal network hosts flagged by the threat detection system. The oversight - a missing session check on one endpoint while all sibling endpoints (`/events`, `/counts`, `/hunt`, `/meta`, `/geo`) correctly required authentication - was confirmed by the vendor and patched in version 3.1 the same day it was reported. A public proof-of-concept exploit is available, making exploitation trivially scriptable against exposed instances.
Authorization bypass in subhajitkhan's online-clinic-management-system lets a remote, unauthenticated attacker take over an administrator session by manipulating the adminmail argument processed by session_start() in adminappview.php, with no password or token required. Publicly available exploit code exists and the maintainer has not responded to the issue report filed against the project, so no fixed release is available. With CVSS 4.0 base metrics of AV:N/AC:L/PR:N/UI:N and E:P, impact is scored low across confidentiality, integrity and availability, but the resulting admin session can expose patient and appointment records.
Improper access control in PHPGurukul Hostel Management System 3.0 allows an attacker to bypass authorization checks in the admin login handler /admin/includes/checklogin.php by manipulating the ID parameter, granting unauthorized access to administrative functionality. Exploitation is remotely reachable and publicly available exploit code exists (tracked via a GitHub PoC issue and VulDB entry), though the per-component impact is limited to low confidentiality, integrity and availability loss. EPSS/KEV signals are absent from the provided data, and the published CVSS 4.0 base metrics (AV:N/AC:L/PR:L/UI:N, all impacts Low) indicate a modest real-world risk rather than mass-exploitation potential.
Yao (YaoApp) through v1.0.0-rc22 allows any authenticated user to read complete team records via the GET /user/teams/:id endpoint, which authenticates the caller but never verifies team membership. Attackers who hold a low-privilege account and know or guess a team identifier can retrieve team name, description, owner information and settings. The flaw is remotely reachable with low complexity but yields only low confidentiality impact (CVSS 5.3), and no public exploit code or CISA KEV entry was identified at time of analysis.
Let me synthesize this into the required JSON. Key facts: - CVE-2026-91773, Soft Serve (charmbracelet/soft-serve), Git LFS lock metadata disclosure. - CWE-639 Authorization Bypass Through User-Controlled Key (IDOR) - CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N → 5.3 - Affected: 0.7.1 through 0.11.6 (fixed in 0.12.0) - Patch: vendor available; commit e34914699128c937afad167d43ccb5310e48b319 adds repo_id scoping. - No KEV, no POC noted explicitly. But commit includes tests. No EPSS given. - Tags: Authentication Bypass, Soft Serve. Product name: "Soft Serve" (charmbracelet soft-serve) — 2 words. Good. Prevalence: Soft Serve is a self-hosted Git server — niche. "low" or "rare". It's a fairly well-known project in the Charm ecosystem but not widely deployed enterprise. I'll say "low" with basis "self-hosted Git server, niche deployment footprint". Assessed CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N = 4.3. Wait: CVSS 3.1 with PR:L, C:L → base score. Let me compute: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Exploitability = 8.22 * AV(0.85) * AC(0.77) * PR(0.62) * UI(0.85) = 8.22*0.85=6.987; *0.77=5.38; *0.62=3.335; *0.85=2.835. Impact sub-score for C:L only: ISS = 1 - [(1-0.22)*(1-0)*(1-0)] = 0.22. Impact = 6.42*0.22 = 1.412. Base = roundup(min(1.412+2.835, 10)) = roundup(4.247) = 4.3. Fine. CVSS 4.0: matches provided: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Attack chain: Authenticate to Soft Serve → Access any repo with write permission (own repo) → Enumerate LFS lock IDs via lock list endpoint → Retrieve lock metadata from private repos → Recover file paths, usernames, timestamps. 5 steps. Exploitation conditions: requires authenticated account with write access to at least one repository; the LFS lock list endpoint accepts `id` query param; target must be using Soft Serve Git LFS locks feature with locks present in private repos. Limits: read-only (confidentiality only), no ability to modify/delete others' locks? Actually
Improper authentication in the admin Dashboard controller of PHPGurukul Blood Donor Management System 1.0 lets a remote, unauthenticated attacker reach administrative functionality by calling the controller's constructor route directly, bypassing the login/session check. Successful abuse exposes donor and blood-stock data and allows modification of records, giving low but real confidentiality, integrity and availability impact. Publicly available exploit code exists and the vendor has not published a fixed release, so every internet-facing deployment of version 1.0 should be assumed reachable by automated scanners.
Authenticated, low-privileged users of Webkul Bagisto 2.4.9 can obtain sensitive information belonging to other customers by manipulating object identifiers in the add-to-cart API and the downloadable-product fulfilment flow. The flaw is an insecure direct object reference (CWE-639) rated CVSS 6.5 with a network vector, low privileges, and confidentiality-only impact; no CISA KEV entry or public exploit code is associated with this CVE in the available data, so it is currently a patch-and-harden issue rather than an active-exploitation emergency.
Arista EOS network switches permit an authenticated 802.1X supplicant on an adjacent Layer 2 segment to send traffic unrestricted by its assigned ACL during a brief race window - spanning milliseconds to seconds - between the completion of the authentication handshake and the point at which the switch fully enforces the authorization policy. The flaw is classified under CWE-862 (Missing Authorization) and affects all EOS releases through 4.33.7.1M as well as specific 4.34.x and 4.35.x branches. No public exploit code has been identified and the issue is not listed in the CISA KEV catalog; its real-world impact is limited by adjacency requirement, authentication prerequisite, and the very short exploitation window.
HTTP CONNECT tunnel authentication bypass in goproxy through v15.3 permits unauthenticated remote clients to establish arbitrary TCP tunnels through a proxy that has basic authentication configured, completely nullifying the access control mechanism. Attackers send CONNECT requests without an Authorization header and the proxy accepts them unconditionally, enabling relay of arbitrary TCP traffic to otherwise-restricted destinations. No public exploit code or active exploitation has been identified at time of analysis, but the attack requires no credentials, no user interaction, and only basic HTTP client capability.
Arista EOS devices simultaneously running 802.1X port authentication and the RADIUS proxy feature with dynamic authorization can be manipulated by a low-privileged adjacent attacker to suppress RADIUS Change-of-Authorization (CoA) and Disconnect-Request messages targeting locally authenticated 802.1X sessions. By inducing a crafted RADIUS packet through a configured RADIUS proxy client interface, an attacker causes the switch to discard legitimate session-revocation orders from a RADIUS server or NAC system, allowing revoked endpoint sessions to persist on the network indefinitely. Arista discovered this issue internally and reports no known malicious exploitation in customer environments; no public exploit code exists at time of analysis.
IBM Sterling B2B Integrator (6.2.0.0 through 6.2.0.6_2, 6.2.1.0-6.2.1.2, 6.2.2.0-6.2.2.1) and IBM Sterling File Gateway Standard Edition in the same version ranges contain an improper authentication flaw (CWE-287) that lets a remote authenticated attacker bypass security restrictions. The CVSS 3.1 base score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N), indicating a low-privilege authenticated network attacker can gain limited read and modify capability without user interaction, but no confidentiality-integrity-availability loss beyond partial. There is no CISA KEV listing, no public exploit code identified, and no EPSS score supplied in the available intelligence, so this appears to be a targeted-patch issue rather than a mass-exploitation emergency.
IBM Sterling Secure Proxy versions 6.2.0.0 through 6.2.1.2 enforce authorization for certain administrative user interface components only on the client side, so an attacker who already holds a valid low-privileged account can cause the browser to render admin-only UI elements that should have been hidden. The result is a limited information disclosure (CVSS 4.3, C:L, no integrity or availability impact) rather than full administrative takeover, and no public exploit code or CISA KEV entry was identified in the supplied intelligence. Because the flaw is a missing server-side authorization check (CWE-285), any authenticated user of the affected deployment can probe it trivially with low attack complexity.
Apple macOS contains an improper access-control logic flaw in state management that allows a locally running app to read protected user data outside of its intended permission scope. The issue affects macOS Sequoia, macOS Tahoe and the macOS 27 (Golden Gate) line prior to the fixed releases, and is remediated in macOS Sequoia 15.8, macOS Tahoe 26.7 and macOS Golden Gate 27. The CVSS vector (AV:L/AC:L/PR:N/UI:R, C:H/I:N/A:N) shows this is a local, confidentiality-only issue requiring a user to launch or open the malicious app, with no public exploit identified at time of analysis and a low EPSS score of 0.18% (8th percentile) — real-world exploitation pressure is currently minimal.
Improper state management in Apple macOS (all versions prior to macOS 27 "Golden Gate") lets a locally installed application reach sensitive user data that normal macOS privacy and access controls are supposed to protect. The attack is local and needs the victim to launch the malicious app (AV:L, UI:R, PR:N), and the impact is confidentiality-only (C:H/I:N/A:N), which yields a moderate CVSS of 5.5. The issue is fixed in macOS 27 per Apple's advisory, EPSS is very low (0.14%, 3rd percentile), there is no CISA KEV listing, and no public exploit code has been identified.
Gatekeeper protection bypass in Apple macOS lets a locally executed, unprivileged application evade the operating system's notarization and quarantine checks, allowing unsigned or unnotarized code to run that Gatekeeper would normally block. The flaw is a logic/state-management error (CWE-693, protection mechanism failure) affecting macOS releases prior to macOS 27 (Golden Gate); exploitation requires the attacker to already possess a local foothold or to persuade a user into launching a malicious app, since the CVSS vector is AV:L/PR:L with no remote or unauthenticated path. Apple has shipped a vendor fix referenced in advisory 149035, EPSS is low at 0.16% (6th percentile), and no public exploit code or confirmed active exploitation has been identified at time of analysis - the real risk is as a chaining primitive to run code that Gatekeeper would otherwise reject.
A permissions-validation flaw (CWE-863) in Apple macOS versions prior to 27 (Golden Gate) and Xcode versions prior to 27 allows a locally installed app to reach user-sensitive data it should not be authorized to read. The issue is a local, confidentiality-only defect rated CVSS 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N): no privileges are needed, but the attack requires the victim to run the malicious application. Apple has released fixes in macOS 27 and Xcode 27; there is no CISA KEV listing, no public exploit code identified at time of analysis, and EPSS is very low at 0.16% (5th percentile), so real-world exploitation is unlikely to be widespread.
An improper access-control flaw in Apple macOS allows a locally running application to bypass authorization checks and read sensitive user data it should not be able to reach, with the fix delivered in macOS Sequoia 15.8 and macOS Golden Gate 27. Exploitation is local only and requires user interaction (the victim must launch the malicious or trojanized app), so the CVSS impact is limited to confidentiality (5.5 Medium). EPSS is negligible at 0.16% (5th percentile), there is no CISA KEV listing and no public exploit code identified at time of analysis, making this a routine update rather than an emergency patch.
Improper access control in Apple's Keychain service lets a locally installed app delete credentials stored by other applications on iOS 27, iPadOS 27, macOS Golden Gate 27, and visionOS 27 (all versions prior to these releases). The bug is fixed by removing the vulnerable code path; it is rated CVSS 5.5 with integrity-only impact, and there is no public exploit or CISA KEV confirmation at time of analysis (EPSS 0.15%).
Improper authorization checks in Apple's headphone motion data handling allow a locally installed app to read motion sensor data from connected headphones without prompting the user for consent, affecting iOS/iPadOS 26.7 and 27 and earlier, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, tvOS 27 and watchOS 27 and earlier. Exploitation requires a malicious or compromised app and user interaction, and the impact is limited to confidentiality of headphone sensor data (CVSS 5.5, C:H/I:N/A:N). Apple has shipped fixes in all affected operating systems; EPSS is low (0.20%, 10th percentile), there is no CISA KEV listing and no public exploit code identified at time of analysis.
An authorization flaw in Apple's operating systems lets a locally installed malicious app bypass Privacy preferences on affected iOS, iPadOS, and macOS builds. Apple addressed the issue through improved state management in iOS 18.7.10, iPadOS 18.7.10, iOS 27, iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.7.8, and macOS Sonoma 14.8.8. The CVSS 3.1 base score is 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N), EPSS is 0.21% (11th percentile), there is no CISA KEV listing and no public exploit code identified at the time of analysis.
Privacy preference bypass in Apple macOS allows a locally running application with normal (low) user privileges to circumvent the TCC consent controls that gate access to protected user data, affecting macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27. The attack surface is entirely local and non-network-facing: an attacker must first get an untrusted or malicious app installed and running on the device, after which no further user interaction is needed, and the resulting impact is capped at low confidentiality and low integrity with no availability loss and no privilege escalation or system compromise. Exploitation risk is low - EPSS is only 0.18% (8th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis - while vendor-released fixes are already available for all three affected release trains.
A locally installed application on macOS versions prior to macOS Golden Gate 27 can bypass Gatekeeper code-origin and notarization checks, weakening the platform control that is supposed to stop untrusted apps from launching. The flaw is assessed at CVSS 4.4 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N), meaning it requires local presence and normal user privileges, and the resulting impact is limited to partial confidentiality and integrity loss rather than code execution or denial of service. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (no CISA KEV listing); EPSS is only 0.18% (8th percentile), and Apple has released a fix in macOS Golden Gate 27. Per the independent assessment, this is a genuinely low-priority issue despite the 'Authentication Bypass' tag.
Local information disclosure in Apple macOS before Golden Gate 27 allows an installed app to bypass system pasteboard sandbox restrictions and read sensitive pasteboard data, resulting in confidentiality impact only. The flaw is not remotely exploitable; it requires attacker-controlled code already running locally, typically a malicious or compromised app that the user has installed and launched. Apple fixed it in macOS Golden Gate 27, and no public exploit was identified at time of analysis (EPSS 0.17%, CVSS 5.5 Medium).
Incorrect authorization handling in Apple's iOS, iPadOS, macOS, and tvOS lets a locally installed app reach sensitive user data that should be fenced off by the platform's state and sandbox checks. The flaw is a local, low-privilege issue (CVSS 5.5, AV:L/PR:L) requiring a malicious or compromised app already running on the device — no network vector and no user interaction beyond launching the app. Apple has shipped fixes in iOS/iPadOS 26.7 and 27, macOS Sequoia 15.8, macOS Tahoe 26.7, macOS Golden Gate 27, and tvOS 27; EPSS is very low (0.17%, 6th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis.
Local applications on macOS releases prior to Golden Gate 27 can bypass the Apple Intelligence security and consent prompts, evading the authorization gate that is supposed to require explicit approval before protected Apple Intelligence functionality is reached. Exploitation is not remote: an attacker must first get a malicious or abusable app onto the machine and running under normal user privileges (CVSS AV:L/PR:L, no user interaction at exploit time), and it is only meaningful where Apple Intelligence is present and enabled. The issue is a low-urgency local authorization flaw rather than an emergency - CVSS 5.5, EPSS 0.15% (5th percentile), no CISA KEV listing, and no public exploit identified at time of analysis - though Apple has addressed it with improved state management in macOS Golden Gate 27.
Improper access control in Apple iOS, iPadOS, and macOS lets a locally installed application running with low privileges read sensitive user data, with no user interaction required, affecting iOS and iPadOS before 26.7 and before 27 and macOS before Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. Apple fixed the authorization flaw (CWE-285) through improved access control as part of its 26.7/27 release cycle, so vendor patches are available for every affected platform. At a CVSS base score of 5.5 and an EPSS score of only 0.19% (9th percentile), this is a moderate-severity, low-priority local authorization issue; no public exploit code has been identified at time of analysis.
Archive expansion on Apple operating systems can slip past Gatekeeper's file-quarantine checks, allowing unsigned or un-notarized code inside a crafted archive to run without the normal block or warning prompt; macOS (Sequoia, Tahoe and Golden Gate), iOS/iPadOS, visionOS and watchOS are all affected and remediated in the 26.7/27 and 15.8 releases documented in Apple advisories 149034-149043. The flaw is local in nature (CVSS:3.1/AV:L/AC:L), requires the archive to actually reach and be expanded on the device, and carries bounded impact (C:L/I:L/A:N) because it defeats a trust warning rather than granting elevated execution - though the vendor's vector assumes low privileges and no user interaction while our independent assessment treats the expand/open step as user-driven. There is no public exploit identified at time of analysis and no CISA KEV listing, with EPSS at 0.18% (8th percentile), making this a genuinely low-priority issue despite the security-relevant nature of a Gatekeeper bypass; exploitation status is 'no public exploit identified at time of analysis'.
Improper access control in Apple macOS allows an application already running on the system to reach sensitive user data that should have been protected by a platform check, affecting macOS versions prior to Sequoia 15.8, Tahoe 26.7, and Golden Gate 27. The flaw is local-only and authenticated in the sense that it requires a malicious or compromised app executing with standard (non-root) user privileges (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 5.5) - there is no remote vector and no additional user interaction beyond launching the app, but confidentiality impact is rated High while integrity and availability are untouched. Apple does not disclose which specific protected resource or entitlement check is bypassed, so all pre-patch installs should be treated as affected. Risk is genuine but modest: EPSS is 0.17% (6th percentile), no public exploit code has been identified at time of analysis, and the vulnerability is not confirmed actively exploited (no CISA KEV listing); vendor patched versions are already available.
Improper authentication state management in Apple iOS and iPadOS versions prior to 27 lets someone with physical access to an already-unlocked iPhone or iPad view stored Wi-Fi passwords without supplying credentials. The flaw is purely physical (CVSS:3.1/AV:P/AC:L/PR:N/UI:N), carries a high confidentiality impact (C:H) but no integrity or availability effect, and does not affect devices running iOS 27 or iPadOS 27, where Apple corrected the state-handling logic. Exploitation is confirmed to be neither remotely reachable nor scalable, EPSS is only 0.21% (11th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis.
An improper authorization and state-management gap in Apple's Bluetooth stack lets a locally running app on affected macOS and watchOS builds reach Bluetooth device information it should not be able to read. Affected systems are macOS Golden Gate before 27, macOS Sequoia before 15.8, macOS Tahoe before 26.7, and watchOS before 27; the attacker must already have an app executing with app-level privileges (CVSS vector PR:L, with our assessment placing the attack vector as local rather than adjacent), so this is not an unauthenticated or remote path. Impact is confined to confidentiality of Bluetooth device data (C:L, no integrity or availability effect) and the issue is low severity overall - CVSS 3.5, EPSS 0.16% (6th percentile), no CISA KEV listing, and no public exploit identified at time of analysis.
Bypass of on-device network restrictions in Apple iOS/iPadOS, macOS Golden Gate, visionOS, and watchOS builds prior to version 27 allows a locally installed, already-running app to reach network resources the operating system should have blocked, producing low confidentiality and low integrity impact with no availability effect. Exploitation requires an app that is already installed and executing with normal, authenticated app privileges on the target device (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, score 4.4); there is no remote or unauthenticated attack path, no public exploit identified at time of analysis, and EPSS is a low 0.21% (11th percentile). Apple has shipped vendor-released fixes in iOS 27, iPadOS 27, macOS Golden Gate 27, visionOS 27, and watchOS 27.
Gatekeeper enforcement in Apple macOS can be bypassed by a malicious application that is delivered locally and opened by the user, letting the app run without satisfying macOS's normal code-signing and notarization checks. The flaw is a logic error (CWE-693, protection mechanism failure) affecting macOS builds prior to Golden Gate 27, Sequoia 15.8, Tahoe 26.6 and Tahoe 26.7; CVSS 5.5 reflects an integrity-only, non-privileged local impact that requires user interaction and grants no direct privilege escalation or confidentiality loss. No public exploit code has been identified at time of analysis and EPSS is low at 0.21% (11th percentile), so the practical value of the bug is as a stage in a broader malware delivery chain rather than a standalone compromise.
Apps already running on macOS versions prior to Golden Gate 27 can modify Privacy (TCC) preferences they are not authorized to change, letting a malicious app grant itself access to consent-gated resources such as the camera, microphone, or other protected data without ever prompting the user. The root cause is an incorrect-authorization weakness (CWE-863) that Apple addressed by adding restrictions to the permission check, so exploitation is not remote: the attacker must first deliver and run code on the host (AV:L, PR:L, UI:N), making this primarily a post-compromise, integrity-only escalation of an app's privacy privileges (C:N/I:H/A:N). EPSS is only 0.17% (7th percentile), there is no CISA KEV entry and no public exploit identified at time of analysis, and a vendor-released fix exists in macOS Golden Gate 27.
Local applications running on unpatched Apple macOS builds can bypass permission checks and read sensitive user data they are not authorized to access. The issue affects macOS Sequoia before 15.8, macOS Tahoe before 26.7, and macOS Golden Gate before 27, and was resolved through improved permissions validation in those releases. No public exploit code has been identified at time of analysis and the EPSS score is negligible (0.16%, 6th percentile), making this a genuine but low-priority, confidentiality-only local flaw.
Gatekeeper code-signing enforcement in Apple macOS can be bypassed by an app that is already present and running on the host, allowing it to launch untrusted code that macOS would normally block. The affected software is macOS prior to the fixed builds (Sequoia before 15.8, Tahoe before 26.7, and the next-generation release line before 27), and the CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N describes a local attack requiring an attacker to have already achieved normal user-level execution, with low confidentiality and integrity impact and no availability impact. No public exploit has been identified at time of analysis and there is no CISA KEV listing; EPSS is 0.21% (11th percentile), consistent with a low-to-moderate, locally-scoped issue rather than an urgent priority.
Improper permission checks in macOS snapshot handling allow a locally installed app to read protected user data, an issue Apple resolved with stronger permissions logic in macOS Golden Gate 27. The flaw is a local access-control problem (CWE-284) that requires user interaction but no special privileges (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, base score 5.5), and it carries a low EPSS of 0.19% (9th percentile). No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, so this is best treated as a moderate-severity confidentiality issue rather than an urgent priority.
Holding a locked iPhone or iPad, an attacker can reach a lockscreen-accessible interface that improperly passes an authentication check, allowing sensitive user information to be viewed without the passcode being entered. The flaw is a logic error classed as CWE-287 (improper authentication) that affects iOS and iPadOS builds prior to 26.7 and 27, and Apple has shipped fixes in iOS/iPadOS 26.7 and iOS/iPadOS 27, so it is fully remediated by updating. Exploitation requires hands-on physical possession of the locked device and cannot be performed remotely or at scale; EPSS is 0.17% (6th percentile) and no public exploit has been identified at time of analysis, making this a low-to-medium real-world priority driven mostly by confidentiality exposure on lost or stolen devices.
Unauthorized local network access on Apple macOS (all releases prior to Golden Gate 27) lets a malicious or compromised application communicate with local network devices without triggering the macOS Local Network consent prompt. The root cause is improper permission state management (CWE-284), and exploitation is strictly local: the user must launch the offending app (CVSS UI:R), with no remote or unauthenticated path. The independent assessment downgrades confidentiality impact to Low relative to the published CVSS 5.5, limiting practical consequences to reconnaissance of LAN-adjacent devices; no public exploit code has been identified and EPSS is only 0.14% (4th percentile), consistent with a low-priority, targeted issue. Apple has fixed the flaw in macOS Golden Gate 27.
Sensitive user data disclosure in Apple iOS and related platforms allows a locally installed malicious app to bypass entitlement checks and access protected data, affecting Safari before 27, iOS/iPadOS before 26.7 and 27, macOS before Golden Gate 27, and visionOS before 27. The flaw requires local app installation and user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R) and only impacts confidentiality (C:H) with no integrity or availability effect. No public exploit has been identified at time of analysis, and EPSS is 0.18% (7th percentile), indicating low exploitation likelihood.
A sandboxed application running on Apple iOS/iPadOS, macOS Golden Gate, tvOS, visionOS, or watchOS can bypass authorization checks and read contents of the System Keychain, exposing stored secrets such as credentials, certificates, and tokens. The flaw stems from incorrect authorization combined with faulty state management (CWE-863) and affects all versions prior to the 27 release train; the platform owner has shipped fixes in iOS 27, iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27, and watchOS 27. The CVSS v3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, score 5.5) is consistent with our independent assessment: this is a genuine but locally-scoped access-control defect that requires an attacker to get a sandboxed app onto the device and have the user launch it (UI:R), so it cannot be triggered remotely over the network. EPSS is 0.16% (6th percentile) and no public exploit code has been identified at time of analysis, with no CISA KEV listing - impact is limited to confidentiality (keychain disclosure) with no integrity or availability effect, and patched 27-or-newer systems are not exposed.
Authorization bypass in Apple macOS allows a locally-running app to read sensitive user data without the user's consent, affecting macOS versions below Sequoia 15.8, below Tahoe 26.7, and below Golden Gate 27. Exploitation requires an attacker to first get a malicious or compromised application onto the machine and running under a standard, non-administrative user account (CVSS 3.1 AV:L/PR:L/UI:N), so this is not remotely reachable and no user interaction is needed once that app executes. Impact is limited to confidentiality of user data (C:H, I:N, A:N) - there is no code execution, privilege escalation, or system modification, and the EPSS score of 0.17% (6th percentile) plus the absence of KEV listing indicate no public exploit identified at time of analysis; Apple has released patched builds.
Gatekeeper protection in Apple macOS can be bypassed by a malicious application, allowing unsigned or unnotarized code to launch on unpatched Macs. The flaw is a state-management logic error in the Gatekeeper check, rated CVSS 5.5 (AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N): exploitation is local and requires the victim to download and open an attacker-controlled app, so it depends on user interaction rather than a remote network path, and it yields no confidentiality or availability impact by itself - it must be chained with a malicious payload. Affected systems are macOS versions below Golden Gate 27, Sequoia 15.8, and Tahoe 26.7; there is no public exploit identified at time of analysis, EPSS is low at 0.18% (8th percentile), and no CISA KEV entry exists.
An incorrect authorization check in Apple macOS lets an application already running on a Mac read sensitive user data it should not be able to reach, an impact limited to confidentiality with no code execution, modification, or denial of service. Exploitation requires local code execution on the target (the assessed vector is AV:L/PR:L/UI:N), so it is only reachable by a malicious or attacker-controlled app already present on the device, and only on unpatched systems below macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27. Apple has released fixes in macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27; no public exploit code or confirmed active exploitation has been identified, and EPSS is low at 0.19% (9th percentile), making this a moderate, locally-scoped risk rather than an urgent priority.
Improper access control in Apple iOS and iPadOS, macOS Tahoe, and visionOS lets a locally installed app read user-sensitive data that it should not be able to reach. The flaw (CWE-284) stems from insufficient validation checks and is remediated in iOS/iPadOS 26.6, macOS Tahoe 26.6, and visionOS 26.6; the assessed vector (CVSS 5.5, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) means exploitation requires the victim to install and launch a malicious app on an unpatched build, with no remote attack path and no integrity or availability impact. The attacker's app needs no special privileges, but there is no public exploit identified at time of analysis and EPSS is low at 0.19% (9th percentile), so this is a genuine but low-priority confidentiality issue.
Improper access control (CWE-284) in Apple iOS, iPadOS, and macOS allows a locally installed app to read user-sensitive data outside the permission boundary the operating system is supposed to enforce, an information-disclosure impact rated CVSS 5.5 (confidentiality High, integrity None, availability None). Exploitation is local and requires user interaction: the attacker must first get a malicious or compromised app onto the device and convince the user to launch it (AV:L, PR:N, UI:R), so there is no remote, network-triggerable, or self-propagating path. Apple has released fixes in iOS 26.7, iPadOS 26.7, iOS 27, iPadOS 27, macOS Sequoia 15.8, macOS Tahoe 26.7, and macOS Golden Gate 27; no public exploit code has been identified at time of analysis and EPSS is low at 0.17 percent (7th percentile), with no CISA KEV listing.
Persistent device identifier disclosure in Apple iOS, iPadOS, macOS, tvOS, visionOS and watchOS stems from an incorrect authorization check that lets an ordinary, unprivileged installed app read identifiers it should not be able to access (CWE-863, CVSS 5.5, C:H/I:N/A:N). Exploitation is local-only (AV:L, PR:N) and requires user interaction to install and launch a malicious or compromised application on a device running an unpatched OS; there is no remote or network path, and no public exploit code has been identified at time of analysis, with EPSS at 0.17% (7th percentile) and no CISA KEV listing. Apple has released fixed versions and the impact is confined to confidentiality/privacy rather than code execution or data modification.
Improper access control in Apple's operating system family (iOS/iPadOS, macOS, tvOS, visionOS, watchOS) lets a locally installed app bypass intended permission restrictions and read sensitive user data it should not be able to reach. Apple addressed the flaw with additional restrictions in iOS 26.7/iPadOS 26.7, iOS 27/iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27, and watchOS 27. Exploitation requires the attacker to already run code on the device as an app (PR:L, AV:L), and no public exploit code or active exploitation has been identified; EPSS is only 0.20% (10th percentile) and CISA SSVC records exploitation as 'none'.
An improper authorization flaw in Apple iOS/iPadOS and macOS Tahoe allows a locally installed application to reach sensitive user data that the platform's authorization state checks should have blocked. Apple addressed the flaw through improved state management, shipping fixes in iOS 26.6, iPadOS 26.6, and macOS Tahoe 26.6 for all versions prior to those releases. The issue is local-only (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, 5.5) with confidentiality impact only; EPSS is 0.15% (5th percentile), CISA SSVC rates exploitation as 'none' and technical impact as 'partial', and no public exploit code was identified at time of analysis.
An incorrect-authorization flaw in Apple's Bluetooth state management allows an already-installed app to obtain Bluetooth access it was never granted, undermining the platform's per-app permission model on iOS 27, iPadOS 27, macOS Golden Gate 27, tvOS 27, visionOS 27 and watchOS 27 - but only on versions prior to those releases. Apple fixed the issue through improved state handling and published coordinated advisories for every affected platform; a local attacker or malicious app is required, so this is not remotely reachable without code execution already on the device. No public exploit code has been identified and EPSS is very low (0.20%, 10th percentile), so this rates as a patching-hygiene item rather than an emergency.
Missing authorization in the A2A Java SDK (a2aproject/a2a-java) 1.2.0 allows a caller with a valid account to invoke the ListTasks operation without the list-scoped read check that guards other task operations, so task listings are returned to principals that the configured TaskAuthorizationProvider may have intended to reject entirely. The flaw lives in AuthorizationRequestHandlerDecorator.onListTasks in server-common, which delegated to the handler without first consulting the authorization provider for the list scope, leaving protection to per-task filtering inside the TaskStore. It is fixed in release 1.3.0 (tag v1.3.0.Final, commit e9a1abf9c90c02b16d17293afdc3cc2f555d63a6); CVSS 4.0 base is 5.3, there is no CISA KEV listing and no public exploit code identified at time of analysis.
An authentication bypass in IBM WebSphere Application Server 9.0 and 8.5 allows an attacker on an adjacent network segment to reach and invoke an administrative console servlet without valid credentials, because the servlet is missing the authorization check that should gate it (CWE-862). Successful exploitation gives low-level confidentiality and integrity exposure plus a high availability impact on the affected server. IBM has released a vendor patch, and there is no CISA KEV listing, no publicly available exploit code, and no EPSS signal in the supplied data, so the practical risk is concentrated in environments where the admin console is reachable from an untrusted adjacent network.
Authentication bypass in IBM WebSphere Application Server 8.5 and 9.0 allows an unauthenticated attacker positioned on an adjacent network segment to reach request-handling functionality that performs no authorization check (CWE-862) and read sensitive information from the response. IBM has released a vendor patch, and there is no public exploit code or CISA KEV entry associated with this issue at time of analysis, so exploitation is not confirmed actively exploited. CVSS rates it 6.5 with confidentiality-only impact and PR:N/UI:N, but no EPSS score was supplied, leaving real-world exploitation likelihood unquantified.
Authorization bypass in IBM WebSphere Application Server 8.5 and 9.0 lets an attacker positioned on an adjacent network segment reach functionality without the required authorization checks, resulting in limited (low) confidentiality exposure with no integrity or availability impact. The published CVSS 3.1 score is only 3.1 (AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N), reflecting that exploitation demands network adjacency and a high-complexity precondition rather than an internet-facing attack. There is no CISA KEV listing, no public exploit code identified in the provided sources, and an EPSS score was not supplied; IBM has published a fix. Note the tension between the 'authorization bypass' label and the very low scored impact — the advisory's own severity framing should be verified directly against the IBM support page.
An authentication bypass in IBM WebSphere Application Server 8.5 and 9.0 allows remote attackers to reach protected resources without valid credentials when the XD or Intelligent-Management features are in use. Successful exploitation yields unauthorized access to confidential data (C:H) with no direct integrity or availability impact, consistent with the CWE-650 (trusting HTTP permission methods) classification. IBM has published an advisory and patch (node/7286610); no public exploit code or CISA KEV listing was present in the supplied intelligence, so active exploitation is unconfirmed.
An improper authentication flaw (CWE-287) in IBM Langflow OSS versions 1.0.0 through 1.10.2 lets a remote attacker who already holds a valid low-privileged account change the password of another user's account, resulting in account takeover rather than direct code execution. The CVSS 3.1 score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L), reflecting that exploitation requires an authenticated session and primarily damages integrity and availability of the targeted account. No public exploit code has been identified and the issue is not listed in CISA KEV, but SSVC flags partial technical impact and the vendor has published a fix; the exact patched version string is not enumerated in the available data.
IBM i Navigator for i — the browser-based administration console shipped with IBM i 7.3, 7.4, 7.5 and 7.6 — can be made to ignore the binding that ties an administrative session to the client's source IP address, allowing a remote, unauthenticated attacker (CVSS PR:N/UI:N) to reach sensitive information that should have been confined to a legitimate session. IBM scores the exposure 5.3 with confidentiality-only impact (C:L/I:N/A:N), consistent with a targeted information disclosure rather than a full compromise of the host. Vendor fixes are published, and no public exploit code or CISA KEV entry appears in the supplied intelligence, so this is best treated as a patch-on-schedule hardening item rather than an emergency.
Really Simple Security (formerly Really Simple SSL) before 9.8.2 ships an unguarded profile-page update handler that lets an authenticated low-privileged WordPress user bypass mandatory two-factor authentication indefinitely. By POSTing to the profile update endpoint without the two-factor-authentication field, the attacker skips nonce verification and reaches delete_two_fa_meta(), which resets the grace-period anchor timestamp on every login cycle, so enforced 2FA is perpetually deferred rather than satisfied. The flaw is rated low severity (CVSS 4.0 base 2.3, PR:L, VI:L) and no public exploit code or CISA KEV entry was identified at time of analysis; a vendor patch is available in 9.8.2.
Missing authorization in the Django-CRM bulk case update endpoint (backend/cases/bulk_views.py) allows any authenticated member of an organization to edit, reassign, or close cases belonging to other users. Affected releases are django-crm 1.0 through 1.2; the same code path also skips the model's close-transition validation, so a case can be closed without the recorded approval that the single-case workflow requires. Version 1.3.0 resolves the issue (patch commit 799bb121), CVSS 4.0 rates it 5.3 (AV:N/AC:L/PR:L/UI:N), SSVC records no exploitation and no automatable vector, and no public exploit code has been identified at time of analysis.
Let me synthesize. Product: Siglet / Eclipse Data Plane Core. The description mentions "Siglet" refresh token handler, CPE says eclipse_data_plane_core. Primary product name — 1-3 words. Probably "Eclipse Data Plane Core" or "Siglet". Let me pick "Siglet" — hmm, the CPE is Eclipse Data Plane Core. The description says "In Siglet current and past versions". Siglet appears to be a component within Eclipse Data Plane Core (Eclipse Dataspace Components). Tags list Eclipse Data Plane Core. I'll use "Eclipse Data Plane Core" as primary? The rules say pick primary product. The CPE is the authoritative affected product. But description says Siglet. Hmm. I'll say "Siglet" — actually product_name 1-3 words only. Let me choose "Eclipse Data Plane Core" (4 words? Eclipse, Data, Plane, Core = 4 words). That violates 1-3 words. "Siglet" is 1 word. I'll go with "Siglet". Hmm, but the affected products refer to Eclipse Data Plane Core. Perhaps Siglet is the SSI/token component. I'll use "Siglet" as product name and mention Eclipse Data Plane Core in affected_products. Actually, to be safe, maybe "Eclipse Data Plane Core" — 4 words is over. Let's use "Siglet". CVSS 6.3, vector CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N — network, high complexity, no privileges, no UI, low impact on C/I/A. CWE-290: Authentication Bypass by Spoofing. Issue: refresh token handler does not enforce proof of possession of the issuer DID. So an attacker who obtains a refresh token (or can present a refresh token) without proving possession of the private key corresponding to the issuer DID can redeem it — token theft/replay allows issuing new access tokens. That's authentication bypass by spoofing: the token handler accepts a refresh token without verifying the DID key binding. Affected versions: Eclipse Data Plane Core 0.1.0 ≤ 0.1.3 and commit range a6f7d4cc... < 882fe22d... Patch: Available from vendor. The commit 882fe22db42bc67abfd0304c4cdb141b762c35d1 is likely the fix com
An attribute-read sandbox bypass in the PraisonAI multi-agent framework (pip package praisonaiagents before 1.6.59) lets prompt-influenced Python code reach blocklisted dunder attributes such as __class__, __bases__, __globals__ and __dict__, exposing in-process objects and secrets to the attacker. Exploitation requires the execute_code tool's sandbox mode with approval automatically granted (for example via PRAISONAI_AUTO_APPROVE or the YAML auto-approval path), after which two CPython semantics are chained: runtime string assembly evades the AST blocklist and str.format/str.format_map resolve dotted fields through C-level attribute access that never consults the Python-level _safe_getattr wrapper. The result is a high-confidentiality read primitive rather than a complete in-process execution chain; the vendor has published a fixed release (1.6.59) plus a public GitHub advisory containing a reproducer, and there is no CISA KEV listing indicating active exploitation.
PraisonAI's Server-Sent Events (SSE) server accepts /publish, /events, and /info requests without ever checking the ServerConfig.auth_token value, so any client that can reach the listening port can broadcast arbitrary events into every connected client's stream and read back server configuration and connected-client counts. Affected are praisonaiagents releases prior to 1.6.58 (some package metadata lists 1.6.59 as the fixed version); the npm-style pip package is the delivery vehicle and the flaw only manifests when the optional SSE server mode is started. Public proof-of-concept curl commands are published in the GitHub advisory (GHSA-35w5-pcw4-jx94), but there is no CISA KEV listing and no confirmed active exploitation; CVSS 4.3 with an adjacent-network vector reflects a real but bounded integrity/confidentiality problem rather than remote code execution.
Cache invalidation in novel-plus through 5.3.3 exposes an unauthenticated HTTP endpoint protected only by a hardcoded default password embedded in the application's source-controlled configuration file, allowing any remote attacker who supplies the known default value in the URL path to forcibly invalidate portal caches at will. The root cause (CWE-1392: Use of Default Credentials) means the credential is fully disclosed in the public GitHub repository and a VulnCheck-reported Python POC, reducing exploitation to a trivial one-liner. No vendor-released patch exists as of the latest tagged release v5.3.3, leaving all deployments that have not manually rotated the credential exposed with a publicly available exploit.
Unauthenticated CAPTCHA bypass in SP Page Builder Pro (Joomla extension, versions 5.1.4-6.9.0) allows any remote attacker to defeat form bot-protection by supplying attacker-controlled CAPTCHA parameters directly in the HTTP request. The optin_form addon reads the CAPTCHA type, expected answer, and enabled flag from user-supplied request data instead of the server-stored configuration, reducing verification to a trivially solvable md5($captcha_question) == $captcha_answer check where the attacker supplies both operands. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though SSVC classifies it as automatable, making large-scale scripted abuse realistic.
CAPTCHA verification in SP Page Builder Pro's Contact, Opt-in, and Form Builder addons can be defeated on any Joomla site running versions 3.2.6 through 6.9.0 by submitting the parameter view_type=module alongside any non-empty token string. The addon silently discards the CAPTCHA plugin's actual onCheckAnswer verification result and substitutes a trivially-satisfied non-empty-string check whenever this attacker-controlled parameter is present, rendering all configured CAPTCHA types ineffective for forms placed inside SP Page Builder modules. No public exploit has been identified at time of analysis, but the bypass is trivially automatable per SSVC assessment, requiring only a single parameter change in a standard form POST.
Board-creation permission enforcement is absent from three Mattermost Boards API endpoints-board duplicate, boards-and-blocks, and archive-import-allowing any authenticated user who has been denied board-creation rights to circumvent that restriction and create boards in the workspace. Affected are Mattermost versions 11.9.0, 11.8.x through 11.8.4, 11.7.x through 11.7.7, and 10.11.x through 10.11.22, as confirmed by advisory MMSA-2026-00715. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog; real-world impact is limited to unauthorized board creation with no confidentiality or availability consequence.
Incorrect authorization enforcement in Apache Doris lets any authenticated user read data they were never granted privileges to access, breaking tenant and role isolation in the MPP database. The flaw affects the 2.0.x–2.1.x, 3.0.x, 4.0.0–4.0.7 and 4.1.0–4.1.3 lines, is remotely reachable by any low-privileged account without user interaction, and is rated CVSS 6.5 with confidentiality-only impact. Apache has published fixed releases 4.0.8 and 4.1.4; no public exploit code and no confirmed active exploitation were identified in the available intelligence.
Unauthenticated REST API access on Contec's CPSN-MCB271 series Remote I/O Coupler Unit (Server Type) allows any network-reachable attacker to read industrial I/O sensor values and issue output control commands without credentials. The vulnerability arises from a complete absence of authentication on the device's REST interface, exposing physical process control functions directly over the network. No public exploit code or active exploitation has been identified at time of analysis, though the CVSS 4.0 base score of 6.9 (AV:N/AC:L/AT:N/PR:N/UI:N) reflects a straightforward, condition-free exploitation path.
Missing authentication on the API Command Endpoint in 0x4m4's HexStrike AI (hexstrike_server.py) allows any remote, unauthenticated caller to invoke server-side API commands without presenting credentials. All commits through d689933ff579 in the hexstrike-ai repository are affected; the project uses rolling releases with no discrete versioning, and the maintainer has not responded to the responsible disclosure filed in GitHub issue #223. A public exploit has been disclosed (CVSS 4.0 E:P), lowering the bar for exploitation to any HTTP client with network reach to the exposed server.
Cross-tenant SMTP sender spoofing in N-able Mail Assure (all versions through April 2026) permits any authenticated tenant to specify arbitrary MAIL FROM envelope addresses - including domains belonging to other co-hosted tenants - without the relay enforcing any domain-to-account ownership binding. Because the shared relay is itself listed in the SPF records and DMARC policy of every hosted tenant domain, spoofed outbound messages pass SPF and DMARC validation at recipient mail servers, giving the attack the appearance of fully authorized email. N-able has publicly stated this is intended behavior of its shared relay architecture, making no vendor patch expected. A researcher demonstration gist has been published, and no public exploit or CISA KEV listing exists at time of analysis.
Unauthenticated file upload in Anil-matcha Open-Generative-AI (versions up to 1.0.11/2.0.0) allows any remote attacker to upload arbitrary files - including HTML, SVG, and executable types - to the application's S3 backend via the /api/upload-binary proxy endpoint. The endpoint accepted requests without any API key check and imposed no restrictions on file type or content, as confirmed by the patch commit f013270957f. No active exploitation or public proof-of-concept has been identified at time of analysis; EPSS data was not provided.
The graphiti FastAPI-based graph memory REST API (getzep/graphiti ≤ 0.30.2) shipped its ingest and retrieve routers with zero authentication - no API key, no token, no session check of any kind. Any unauthenticated remote caller with network access to the service can read stored knowledge-graph episodes or inject and overwrite graph data by sending ordinary HTTP requests. No public exploit code has been identified, but the barrier to exploitation is effectively zero: the attack requires only HTTP client access and knowledge of endpoint paths. No KEV listing at time of analysis.
Authentication bypass in Cheshire Cat AI up to version 1.9.2 allows remote unauthenticated attackers to manipulate the `user_id` argument within the `_authorize_http_key` function to circumvent HTTP API key validation entirely. Any publicly exposed Cheshire Cat AI instance is at risk of unauthorized access to its AI agent API, enabling arbitrary interaction with the agent without valid credentials. A proof-of-concept exploit has been publicly disclosed via GitHub issue #1137, and the project maintainers had not responded to the disclosure at time of writing; no patch is available.
Privilege escalation through parameter manipulation in Rizwan17's inventory-management-system allows remote unauthenticated attackers to register accounts with arbitrary privilege levels, including administrative roles, by supplying a crafted `usertype` value to the `createUserAccount` function in `register.php`. The vulnerability stems from the registration handler trusting client-controlled role values without server-side enforcement of permitted self-registration tiers. A public exploit is available via a GitHub issue report, and the vendor has not responded to the coordinated disclosure as of the time of reporting.
Improper access control in Rizwan17's PHP-based inventory-management-system exposes dashboard.php to unauthorized access via manipulation of the `userid` parameter, allowing remote unauthenticated attackers to access other users' data or bypass authentication controls. The affected codebase is identified by commit bfe78a330d01bb26b9daec5dc9ecd5c77900e03f and is distributed as a rolling release with no versioned patch available. A public proof-of-concept exploit has been published in a GitHub issue, and the maintainer has not responded to the responsible disclosure.
Authorization bypass in Apache Storm Logviewer 3.0.0 exposes daemon logs and tenant log file listings to any filter-authenticated user, entirely disregarding the configured `logs.users` and `logs.groups` access controls. A boolean short-circuit in the daemon log authorization path discards the authorizer's decision whenever the daemon-log flag is set, and the daemon log page and download endpoints are reached without consulting an authorizer at all; additionally, the listing endpoints `/listLogs` and `/searchLogs` accept a user argument but never apply it. On a multi-tenant Storm cluster, any user who passes the servlet filter can read nimbus.log, supervisor.log, and other daemon logs-which contain co-tenant topology names, job owners, and configuration fragments-and enumerate all worker log file names. No public exploit identified at time of analysis.
Missing authentication on update endpoints in jaychouchannel's Tourism-Management-System exposes write operations across 12 Spring controllers - including chat messages, forum posts, hotel/restaurant discussions, news, friend links, and bookmarks - to unauthenticated remote attackers. The root cause is confirmed by the patch commit (84d8ec3): the custom `@IgnoreAuth` annotation was incorrectly applied to update-path handlers, causing the authentication interceptor to skip those routes entirely. A public proof-of-concept exists via GitHub Issue #11; no CISA KEV listing has been issued.
Unauthenticated access to the AWS API Gateway endpoint in simalexan/api-lambda-send-email-ses allows any remote attacker to invoke the SES.sendEmail Lambda function without credentials, abusing the deployer's AWS Simple Email Service account to send arbitrary emails. Affected deployments are those built from any commit up to bda6869aa81371d1e872242e74fe7d953edb818d, with no patched release available as the project uses rolling delivery and the maintainer has not responded to the disclosure. No public exploit code or CISA KEV listing exists, but exploitation requires only knowledge of the deployed API Gateway URL and a simple HTTP request.
Hard-coded API token in dromara orion-visor through version 2.5.7 allows remote unauthenticated attackers to bypass the ExposeApi authentication gate enforced by ExposeApiAspect.beforeExposeApi. The static token is now publicly documented in a proof-of-concept writeup on GitHub after the vendor failed to respond to the responsible-disclosure issue report. No public exploit confirmed in CISA KEV at time of analysis, but a POC is available, materially lowering the bar for exploitation.
Improper access control in WARP-Clash-API (vvbbnn00) allows remote attackers to bypass key-based authorization in the Surge subscription handler, gaining unauthorized read and write access to subscription data. The affected function is get_surge_subscription in services/subscription.py, where manipulation of the key argument circumvents access control checks. A public proof-of-concept exploit exists on GitHub, and the product is abandoned with no upstream fix available or anticipated.
Authentication bypass in vvbbnn00's WARP-Clash-API allows unauthenticated remote attackers to circumvent the `authorized` function by manipulating the SECRET_KEY argument, gaining unauthorized access to the API's proxy configuration management functions. All versions up to commit c7bf2360073959861219b422e51ae86411051b46 are affected, and no patch exists because the maintainer has abandoned the project and did not respond to disclosure. A public proof-of-concept exploit is available via a GitHub gist, lowering the bar for exploitation against any internet-exposed instance.
Missing authentication in WWBN AVideo's Live plugin allows unauthenticated remote attackers to inject arbitrary socket notification messages to any administrator whose live stream key is known. The endpoint `/plugin/Live/socketMessageLiveOwner.json.php` validates that the stream *owner* holds admin privileges but performs no caller authentication (`User::isLogged()` is never invoked) and enforces no CSRF token, meaning the caller-identity check is entirely absent. No patch was available at time of publication; VulnCheck reported the issue against commit c3edcc274c389816d434acadac07ee78eaf330c1 and earlier.
Unauthenticated information disclosure in WWBN AVideo through commit c3edcc274c exposes inactive admin menu items and embedded secret query parameters via the unprotected `plugin/TopMenu/menuItems.json.php` PHP endpoint. Any network-reachable attacker can POST a `menuId` parameter to retrieve admin-tool URLs that are hidden from the public navbar, including secret tokens or keys embedded directly in those URLs. While the direct impact is limited confidentiality exposure (CVSS 4.0 VC:L), the leaked secret query parameters represent a stepping stone that could enable follow-on attacks against otherwise-obscured admin functionality. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated API abuse in the WPBot WordPress plugin before 8.5.7 allows any remote attacker to invoke the plugin's AI provider relay endpoints without credentials or a nonce, causing the site's configured third-party API keys (e.g., OpenAI) to issue requests and accrue charges on the site owner's account. The root cause is a complete absence of WordPress capability checks and nonce verification on multiple `wp_ajax_nopriv`-eligible AJAX actions. No public exploit code or CISA KEV listing exists at time of analysis; vendor-released patch 8.5.7 is confirmed available.
Improper certificate validation (CWE-295) in an ICS component's reverse proxy allows a network-adjacent attacker to impersonate the identity provider during token discovery, introspection, and credential exchange, resulting in forged authentication tokens being accepted across the deployment. The affected product is covered under ICS-CERT advisory ICSA-26-254-01, indicating an industrial or operational technology context. No public exploit code or active exploitation has been identified at time of analysis; exploitation requires adversarial positioning on the internal network segment between the reverse proxy and the identity provider.
Reverse proxy authentication passthrough in an ICS inventory-management component exposes the bundled credential-store administrative interface directly to the network when a specific authentication mode is configured. Under this mode, the gateway forwards requests to the credential store's admin UI without enforcing its own authentication, delegating all access control to that third-party interface's own login mechanism. This is the same OT product covered by CISA advisory icsa-26-254-01, which also documents CVE-2026-90456 (default credentials in example config); if both conditions align, an attacker can reach the admin UI of the credential store that gates every other service in the deployment with no gateway-layer resistance.
OCI artifact signature verification bypass in Doco-CD prior to v0.90.1 allows an attacker with write access to a monitored OCI registry tag to circumvent the global OCI_TRUST_POLICY enforcement and deploy unsigned or improperly signed artifacts. By publishing an artifact containing a crafted .doco-cd.yml with oci.verify: false, the attacker exploits a circular trust dependency - the tool reads per-deployment config from artifact contents before verifying that artifact - causing signature checking to be disabled for that same artifact. The vendor-released patch at v0.90.1 enforces a strict no-downgrade trust boundary; no public exploit has been identified at time of analysis.
In the Linux kernel, the following vulnerability has been resolved: svcrdma: Use svc_xprt_put to free listener on create failure svc_rdma_create() calls kfree(cma_xprt) when svc_rdma_create_listen_id() fails. svc_xprt_init() has already acquired a net namespace reference via get_net_track(); kfree bypasses svc_xprt_free() which releases it. Replace the kfree() with svc_xprt_put() so the kref_init birth reference drops to zero and svc_xprt_free() dispatches svc_rdma_free() to clean up properly. sc_cm_id is still NULL at that point; the preceding patch added the necessary NULL guard in svc_rdma_free(). svc_xprt_free() also drops the module reference via module_put(), but the caller _svc_xprt_create() does the same on xpo_create failure, double-putting the single try_module_get() it acquired. Take a compensating __module_get() before the svc_xprt_put() to keep the count balanced, matching the convention in svc_rdma_accept()'s error path.