A path traversal flaw (CWE-22) in HAVELSAN Liman MYS versions 2.3.2 up to but not including 2.3.4-1124 allows remote, unauthenticated attackers to read files outside the intended web-accessible directory, resulting in limited confidentiality exposure. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3), no credentials, privileges, or user interaction are required, so any reachable instance of an affected version is directly exposed to attempts; the impact is confined to partial file disclosure with no write, integrity, or availability effect. No public exploit code was identified at the time of analysis and there is no CISA KEV listing, so exploitation is not confirmed to be active, but the low attack complexity and lack of authentication make the issue practically attractive against internet-exposed Liman MYS deployments. This is a genuine but modest-priority issue.
Workspace ADMIN accounts in Docmost prior to 0.90.1 can mint OWNER-level accounts through the workspace invitation flow, because the invite path never enforces a role ceiling that would stop an administrator from granting privileges above their own. An attacker who already holds the ADMIN role can invite an external email address with the OWNER role; once that invitation is accepted, the resulting account holds the highest privilege level in the workspace, enabling a persistent backdoor OWNER account or the elevation of a colluding external user. Exploitation is access-gated rather than anonymous - it requires an authenticated HIGH-privilege (ADMIN) account and the invitee must accept the emailed invitation (PR:H, UI:R) - and no public exploit code or confirmed active exploitation was identified at time of analysis.
Stored cross-site scripting in Aureus ERP through 1.6.0 allows an authenticated user to upload an SVG file containing embedded JavaScript that is written to the application's public disk and served from the application origin, so the script executes in a victim's browser session when the uploaded file's direct URL is opened. Successful exploitation enables theft of session cookies and CSRF tokens, giving the attacker the ability to act as the victim within the ERP; independent assessment rates this CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (vendor score 5.1), reflecting a cross-site scripted response that requires a second user to open the crafted file URL. Exploitation prerequisites are non-trivial - the attacker must hold an authenticated account with access to a file-upload field and the victim must navigate to the stored file - and no public exploit identified at time of analysis, so this is best handled as a standard patch-cycle item rather than an emergency.
Stored client-side template injection in Krayin CRM through 2.2.6 allows an authenticated user with rights to create or edit web forms to plant Vue.js double-brace template expressions in the form description field, which the Vue template compiler renders without sanitization and which ultimately resolves to arbitrary JavaScript execution in the application origin for any user who views the crafted form. Exploitation requires an authenticated foothold (CVSS:4.0 PR:L / CVSS:3.1 PR:L) plus a separate victim passively rendering the form (UI:P / UI:R), so it is a stored, second-order attack rather than a self-contained remote exploit; impact is confined to client-side script execution in other users' sessions (SC:L/SI:L) with no direct server-side compromise. Severity is moderate - CVSS:4.0 5.1 and the independent assessment's CVSS:3.1 5.1 - and no public exploit code was identified at time of analysis; the issue was reported by VulnCheck and is documented in a public CVE disclosure repository and vendor advisory.
Stored client-side template injection in Krayin CRM through 2.2.6 lets an authenticated user who can create or edit products plant Vue.js template expressions in the product name field, which are then compiled and executed as JavaScript in the browser of any other user who opens the affected product record. Exploitation requires a valid CRM account with product create/edit rights (PR:L) and completes only passively, when a victim views the record (UI:P); impact is confined to the victim's browser and the application's origin, with no server-side compromise or availability effect. No public exploit code was identified in the available intelligence at time of analysis, and there is no evidence of confirmed active exploitation, so this is a genuine but moderate-priority finding rather than a high-severity one.
Stored client-side template injection in Krayin CRM through version 2.2.6 lets any authenticated user who can create or edit a person record plant Vue.js double-brace expressions in the name field, which the client-side Vue template compiler later evaluates in the browser of any other user who opens that record. Successful exploitation results in arbitrary JavaScript execution in the Krayin application origin, allowing theft of data or session material available to the viewing user, but it requires a low-privileged authenticated account to persist the payload and a second user to view the poisoned record, keeping the practical risk at medium severity (vendor CVSS 4.0 5.1; independent assessment CVSS 3.1 5.1). Impact is confined to the victim's browser on the CRM origin with no direct server-side code execution, and there is no public exploit identified at time of analysis and no confirmed active exploitation.
Root-level attackers inside an IBM PowerVM logical partition can corrupt the partition firmware runtime boot configuration stored in NVRAM, leaving that partition unable to boot until an operator manually deletes and recreates the partition configuration. The issue affects PowerVM firmware levels FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, FW1060.00 through FW1060.81, and FW950.00 through FW950.H3, and requires pre-existing root privileges within the target partition (CVSS 3.1 AV:L/PR:H, base score 5.1) with no remote or unauthenticated path to exploitation. There is no public exploit identified at time of analysis and no confirmed active exploitation; the practical risk is post-compromise sabotage or persistence against the attacker's own partition rather than an initial-access vector.
Denial of service in IBM PowerVM Hypervisor firmware affects logical partitions running affected FW1120, FW1110, FW1060, or FW950 levels: an attacker who already holds root inside an LPAR can send a crafted RTAS firmware-to-OS request and crash that partition, making it unavailable. The vulnerability is local-only, requires high privileges, and is contained to the attacker's partition, so other LPARs on the same managed system are not affected. No public exploit was identified at time of analysis, and the CVSS 3.1 score is 5.1 (AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).
Stored client-side template injection in Krayin CRM through 2.2.6 lets an authenticated user who can create or edit leads embed Vue.js double-brace template expressions in a lead's title field, which then execute as arbitrary JavaScript in the browser of any user who opens the poisoned record. The injected expressions reach the client-side Vue template compiler, allowing prototype-chain traversal to the Function constructor and code execution in the application origin, so every subsequent viewer of the lead is affected until the record is sanitized. Exploitation requires valid CRM credentials with lead privileges plus a victim who views the record, and is confined to the browser origin with no server-side code execution; no public exploit code and no confirmed active exploitation (not listed in CISA KEV) were identified at time of analysis, and this is assessed as a moderate, not top-tier, priority.
Reflected cross-site scripting in Paessler PRTG Network Monitor before version 26.2.120.1449 allows an unauthenticated remote attacker to craft a URL targeting a non-existent .htm resource, causing the 403 'Forbidden Path' error page to echo the requested path without encoding and execute arbitrary JavaScript in the context of a victim's active PRTG web session. Exploitation requires user interaction - the victim must click the crafted link while already authenticated to PRTG - and because the PRTG session cookie is not protected with the HttpOnly attribute, a successful attack can read and exfiltrate that cookie to enable session hijacking. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Paessler has released version 26.2.120.1449 to address the flaw.
Trusted-HTML injection in Discourse chat excerpt renderers lets an authenticated user who can both upload files and post chat content embed HTML markup in a filename, which is then rendered unescaped in chat channel lists, chat summary emails, pinned message bars, reply previews, thread previews and other excerpt surfaces. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N, score 5.0) confirms the attacker must be authenticated and that only content integrity is affected, with scope change reflecting that the injected markup renders in contexts beyond the uploader's own message; no public exploit code has been identified at time of analysis and JavaScript execution was not demonstrated under the default Content Security Policy. The practical risk is low and is driven almost entirely by sites that have disabled or relaxed the default CSP, which the advisory notes have increased exposure to script-level attacks. Fixed versions are 2026.1.8, 2026.6.3, 2026.7.2 and 2026.8.0.
An authenticated administrator can read files outside the configured log directory in IBM ContextForge MCP Gateway 1.0.0 through 1.0.8 by abusing a prefix-only path check on the Admin API log-download endpoint GET /v1/admin/logs/file. Because the confinement test uses str.startswith(), a crafted filename that resolves into a sibling directory sharing the LOG_FOLDER string prefix is accepted, exposing .log, .jsonl and .json files - but not arbitrary filesystem content, since only those extensions and prefix-adjacent paths are reachable. Exploitation requires a high-privileged (PR:H) admin account, and no public exploit identified at time of analysis; the C:H confidentiality rating overstates practical risk given the admin prerequisite and the narrow set of reachable files.
Authentication bypass in the Qt VNC Server module allows a remote, unauthenticated attacker to join a shared application session without knowing the configured VNC password by connecting with a modified client that violates the RFB protocol during the handshake, exposing the confidentiality and integrity of the shared session (no availability impact, VA:N). Exposure is conditional: a reachable Qt VNC Server instance must be actively sharing an application session and using the module's built-in password authentication, which is why the independent assessment rates this a genuine but conditional MEDIUM risk (assessed CVSS 3.1 AV:N/AC:H/PR:N/UI:R, C:H/I:H/A:N) rather than an urgent one. No public exploit code was identified at time of analysis (CVSS 4.0 E:U, no CISA KEV listing), and a vendor fix is available.
Local root access inside a guest logical partition (LPAR) on IBM PowerVM systems running affected partition firmware allows an attacker to send a crafted request to the partition firmware runtime and crash it, with possible memory corruption. Rated CVSS 5.1 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H), the flaw affects firmware lines FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, FW1060.00 through FW1060.81 and FW950.00 through FW950.H3; no public exploit has been identified at time of analysis, and the realistic outcome is denial of service to the partition firmware runtime rather than confirmed cross-partition code execution. The guest-root prerequisite makes this a bounded, low-priority risk relevant mainly to multi-tenant or compromised LPARs on shared Power hardware.
Local privilege escalation in Dell Rugged Control Center (RCC) versions prior to 5.2.206 allows a low-privileged attacker with local access to bypass authorization and gain elevated privileges. Exploitation requires an existing low-privileged local account on the host; no public exploit code has been identified, and real-world risk is modest as the flaw cannot be reached remotely and primarily affects multi-user or shared rugged devices.
Label-filter isolation in Dozzle 10.6.5 and earlier is bypassed through the SSE events endpoint (GET /api/events/stream), so any authenticated user - including one explicitly constrained by a users.yml 'filter:' label to a single container scope - receives live CPU/memory/network/disk telemetry and lifecycle metadata for every container on every monitored host. The flaw requires authorization to be enabled (e.g. DOZZLE_AUTH_PROVIDER=simple) and at least one account using per-user label filters, which is the standard multi-tenant or environment-segregated configuration; the attack needs only valid credentials (PR:L) and no special shell/actions/download role or victim interaction. Impact is bounded to metadata and telemetry (container name, image, full label map, and resource counters) rather than log contents, environment variables, or exec/attach capability, which is consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N rating of 4.3 (CWE-200). A lab-only proof-of-concept script is published in the vendor advisory demonstrating the leak; there is no evidence of active exploitation (not in CISA KEV).
Authenticated Termix users can abuse the POST /credentials/:id/deploy-to-host endpoint to reach other users' credential and host records, because the server resolves attacker-supplied credentialId and targetHostId integers without verifying ownership. On instances running 1.7.0 through 2.5.0, this yields limited information disclosure (whether a record exists and its authType) and lets an attacker cause a victim host that authenticates by key to make an outbound SSH connection attempt using the attacker's public key; encrypted passwords and private keys are never exposed, keeping impact consistent with the assessed CVSS 3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). No public exploit identified at time of analysis, and the vendor fixed the authorization check in version 2.5.1.
An authorization bypass through a user-controlled key (CWE-639) exists in Delta Electronics DIAEnergie versions before 1.11.00.022, allowing a low-privilege authenticated user to reference objects or records belonging to other users and read data they are not authorized to access. The flaw is network-reachable (AV:N) and requires no victim interaction (UI:N), but exploitation is gated behind a valid low-privilege session (PR:L), so realistic abuse is limited to malicious insiders, legitimate users exceeding their privileges, or attackers who have already obtained credentials; impact is bounded to confidentiality (C:L) with no integrity or availability effect, giving a CVSS 3.1 base score of 4.3. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), making this a genuine but low-priority weakness rather than a high-severity emergency.
Insufficient input sanitization in HCL Sametime allows remote, unauthenticated attackers to expose limited information to a victim who interacts with attacker-controlled content processed by the product's web interface. According to the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, score 4.3), exploitation cannot occur autonomously - the attacker must socially engineer a target into opening or interacting with crafted input - and the resulting impact is read-only information disclosure with no integrity or availability effect. No public exploit code or confirmed active exploitation has been identified at time of analysis, and HCL's advisory (KB0132652) does not specify which feature, input field, or configuration is affected.
Scoped OAuth MCP tokens issued by TREK before 3.3.0 can pull complete trip summaries - trip metadata, itinerary days, accommodations, and the email addresses of trip members - through the get_trip_summary tool even when the token was never granted the trips:read scope. The issue is an authenticated (CVSS PR:L), low-severity least-privilege bypass: an MCP client holding only an unrelated capability such as weather:read receives data it was never consented to read, defeating the OAuth scope boundary for the token owner's own trips and those of their collaborators. Cross-user trip authorization still holds, so the flaw is not a path to arbitrary users' trips, and no public exploit code was identified at time of analysis; vendor fix is TREK 3.3.0.
Authenticated workspace members in Docmost prior to 0.90.1 can read confidential sync-block content from private spaces via the transclusion/sync-block lookup API, which fails to enforce private space membership before resolving the source page. This authorization bypass through user-controlled key (CWE-639) is rated CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), reflecting low confidentiality impact. No public exploit code has been identified at time of analysis.
Limited information disclosure affects IBM PowerVM Hypervisor firmware on specific service-pack levels (FW1120.00-FW1120.01, FW1110.00-FW1110.31, FW1060.00-FW1060.81, and FW950.00-FW950.H3), where an out-of-bounds read can expose a small amount of adjacent memory content to an attacker. Rated CVSS 4.3 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), the flaw requires no authentication or user interaction but is not reachable across the internet: the attacker must already sit on the same adjacent network segment and be able to reach a hypervisor firmware interface that processes malformed input. Impact is confined to partial confidentiality loss with no integrity or availability effect, and no public exploit identified at time of analysis; IBM has published a vendor fix advisory.
Rendering of attacker-controlled iframes in Discourse is possible on sites that configure wildcard patterns in the allowed_iframes setting, allowing an authenticated user with posting privileges to embed an iframe whose origin is not actually allowlisted. The flaw is a bypass of the wildcard origin check: a crafted URL places the allowlisted suffix after a URL authority separator, so Discourse's text-based match succeeds while the browser resolves a different, attacker-controlled origin, and the iframe is then rendered through a post or a Onebox oEmbed response. Rated CVSS 4.3 (CWE-346, origin validation error) with only a low integrity impact and no confidentiality or availability impact; exploitation requires both a wildcard iframe configuration and posting privileges (PR:L), and no public exploit was identified at time of analysis.
Impact, prerequisites, and exposure for CVE-2026-91769 cannot be determined from the available intelligence; the only confirmed datum is that Ubuntu's security team is tracking this identifier against a package in the Ubuntu archive (reported by vendor:ubuntu). No description, CVSS score or vector, CWE classification, CPE string, affected version range, or configuration prerequisite was supplied, so it is not possible to state whether the flaw is remotely or locally reachable, what privilege an attacker needs (authentication requirements not confirmed from available data), or how severe the consequence is. Exploitation status is unconfirmed: there is no CISA KEV listing and no public exploit identified at time of analysis, but this reflects absence of reporting rather than evidence of safety. Defenders should treat CVE-2026-91769 as an unassessed Ubuntu package issue until the Ubuntu Security Notice and NVD record are published.
Login CSRF in the LoginRadius backend of Python Social Auth (social-core) before 5.0.0 lets an attacker complete a victim's browser session authentication against an attacker-controlled LoginRadius identity, because the OAuth state parameter is never validated during the callback. Only applications that specifically enable the LoginRadius backend are affected; per the assessed vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N, CVSS 4.3) the attacker must possess a valid LoginRadius token and induce user interaction, and the victim's own account is not compromised - they are simply logged in as the attacker, with no confidentiality impact. No public exploit code was identified at time of analysis and there is no CISA KEV listing; the vendor-released fix is social-core 5.0.0, which enforces callback state validation for LoginRadius.
Docmost 0.70.0 through 0.80.0 allows an authenticated low-privileged user with edit rights on an exportable page to disclose attachments belonging to restricted pages in the same space by embedding a forged attachmentId and exporting that page with the includeAttachments=true option. The export flow resolves the attacker-supplied attachment identifier against storage without re-validating ownership, so the restricted file is bundled into the returned ZIP even though a direct download would be denied (CWE-639 IDOR). This is a genuine but low-severity read-only authorization flaw (CVSS 3.1 base 4.3), exploitation is limited to attachments within a space the attacker can already access, no public exploit code has been identified at time of analysis, and the issue is fixed in version 0.80.1.
An out-of-bounds heap read in Espressif ESP-IDF's BlueDroid A2DP sink path (btc_a2dp_sink_handle_inc_media()) affects versions 5.5.5, 6.0.1, and 6.1 on builds where Classic Bluetooth (BR/EDR) and A2DP sink support are explicitly enabled. A paired BR/EDR audio source within Bluetooth radio range can send a malformed A2DP media packet whose layout omits the timestamp field, causing the sink to read a UINT32 past the valid buffer and leak limited adjacent heap contents (CVSS 4.3, AV:A/AC:L/PR:N/UI:N/C:L/I:N/A:N). There is no CISA KEV listing and no public exploit identified at time of analysis, and the reporter explicitly states that arbitrary memory disclosure and code execution are not established, despite third-party tags implying RCE.
Authenticated WordPress users holding Contributor-level access or higher can retrieve administrator-configured Instagram Graph API access tokens from any site running the Spectra Legacy - Gutenberg Blocks plugin at version 2.20.0 or earlier, because the plugin's editor_assets function injects the uag_insta_linked_accounts option into the uagb_blocks_info JavaScript object without performing a capability check. The exposure is gated on a specific deployment state: the separate Spectra Pro plugin must be active and an administrator must already have linked an Instagram account, so sites without that integration have no token to leak and are not meaningfully at risk. Rated CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, CWE-200), this is a real but low-impact, configuration-dependent information disclosure; no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV).
Missing capability checks in the MailerLite - Signup forms (official) WordPress plugin, in all versions up to and including 1.7.21, allow authenticated attackers holding Contributor-level access or higher to create or delete arbitrary signup forms on the affected site. The flaw sits in the forms() method of the AdminController class, which is reachable without verifying that the caller has the capability normally required to manage plugin forms, so any Contributor account is sufficient and no further user interaction is needed. Impact is limited to data integrity - attackers can add or remove form definitions but cannot read data, escalate privileges, or cause site-wide denial of service - and this is a low-severity, routine-patching issue rather than an emergency; no public exploit identified at time of analysis and no CISA KEV listing.
Information disclosure in the Keycloak Admin REST API lets an authenticated delegated administrator holding only basic group/role search privileges enumerate every group assigned to a given role, including groups they are supposed to be unable to see. The flaw (CWE-862, missing authorization) affects the Admin REST API endpoints that return role-to-group mappings in Keycloak, Red Hat Build of Keycloak, and Red Hat Single Sign-On 7, and is rated CVSS 3.1 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) - a read-only confidentiality impact with no integrity or availability effect. It requires valid, privileged-but-scoped credentials and is only meaningful where an organization actually partitions group visibility across delegated admins; there is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing).
Keycloak's Level of Authentication (LoA) step-up enforcement can fail open: when a relying client requires a higher authentication level for a user who already holds an active session at a lower level, a logic error in session re-evaluation causes Keycloak to issue a token carrying the lower acr/LoA claim instead of forcing the required step-up authentication. The impact is a bounded assurance downgrade rather than unauthenticated access - the attacker must already be authenticated (CVSS PR:L) - but it may grant access to sensitive resources whose authorization decisions trust those claims, with low confidentiality and integrity impact and no availability impact (CVSS:3.1 4.2, AV:N/AC:H/UI:N/S:U/C:L/I:L/A:N). Exploitation depends on a deployment that actually configures per-client step-up/LoA and on a specific session-state and re-evaluation timing; no public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV.
Discourse's moderator review queue can expose the contents of private messages to moderators who are not participants in those conversations, because reviewables generated by the optional Discourse AI plugin were not filtered to the audience permitted to access the underlying private-message topic. Affected deployments are those running releases prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0 with the Discourse AI feature producing reviewables; exploitation requires an authenticated moderator account, the AI plugin, and a pre-existing AI reviewable tied to a PM the moderator is not a participant in, so an attacker cannot reliably force the required state. Confidentiality impact is high (and a moderator may additionally close the PM topic or delete a post if the relevant reviewable actions are available), but real-world risk is low-to-moderate given the high privilege required, the dependence on optional functionality, and the opportunistic precondition; no public exploit identified at time of analysis.
Missing project-level authorization in the Task Group APIs of Apache DolphinScheduler allows an authenticated user to read and modify Task Groups that belong to projects they do not have permission to access. Every release before 3.4.3 is affected; the vendor has fixed the flaw in 3.4.3. The issue requires a valid DolphinScheduler account (CVSS PR:L) reachable over the network, so it is chiefly meaningful in multi-tenant or multi-project deployments where project isolation is a security boundary - in single-tenant installs where all users already share project access, the practical impact is negligible. No public exploit code has been identified at time of analysis, and the independent assessment rates the confidentiality and integrity impact as low, making this a genuine but moderate-priority authorization flaw rather than a top-tier emergency.
A specially crafted NFC card or NFC emulator can feed unsanitized data into the web view used by the PaperCut Hive embedded application on Ricoh devices, allowing an attacker with physical access to the device panel to execute code within the application's UI context and potentially trigger unauthorized actions or disclose information. Exploitation requires hands-on physical access to an NFC-enabled device that is configured to use NFC card authentication, and the resulting execution is confined to the embedded app's web view rather than the underlying Ricoh firmware or OS. No public exploit code has been identified at time of analysis and the flaw is not in CISA KEV; with a CVSS 4.0 base score of 3.8 (assessed CVSS 3.1 AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N), real-world risk is LOW despite the 'arbitrary code execution' phrasing in the vendor description.
Parsing a malformed Windows prefetch file through Velociraptor's bundled prefetch library (Velocidex/go-prefetch) can trigger an out-of-bounds condition and crash the parsing operation, an availability-only impact with no data disclosure or code execution. The issue is local and interaction-dependent: exploitation requires that an attacker-supplied or corrupted .pf artifact reach a location the parser processes and that a user or agent run the parse, consistent with the assessed CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L (the vendor-facing score of 3.6 rates it slightly higher with scope change and low integrity impact). No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), so this is a genuinely low-priority defect that should be handled through routine dependency-update hygiene rather than emergency response.
BentoPDF 2.8.6 and earlier ships its Timestamp workflow node with an unvalidated TimeStamp Authority URL, so importing a crafted workflow JSON causes the tool to send the SHA-256 message imprint of a user's PDF to an attacker-chosen endpoint. Exploitation requires the victim to import the malicious workflow and actively run its Timestamp node against a document (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N, score 3.4), and it is only effective in the default self-hosted deployment where VITE_CORS_PROXY_URL is unset and the request bypasses the ALLOWED_TSA_HOSTS proxy check. The leaked digest is metadata only - it can confirm a document matches a known file or correlate the same document across users, but never reveals document contents, and no public exploit has been identified at time of analysis; this is a low-real-risk information disclosure.
Improper handling of sensitive data in the IBM PowerVM Hypervisor partition resource dump interface allows an authenticated administrator on the Hardware Management Console (HMC) or the Power service processor to obtain a limited snapshot of partition processor state, resulting in a confidentiality exposure on the managed system. Affected firmware spans the FW1120.00-FW1120.01, FW1110.00-FW1110.31, FW1060.00-FW1060.81 and FW950.00-FW950.H3 branches. Exploitation requires administrator-level credentials and adjacent-network reachability to the management plane (CVSS 3.1 base score 3.4, vector AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N); there is no public exploit identified at time of analysis, and the practical risk is low because the prerequisite privileged management access is itself a strong barrier and the disclosure is limited in scope.
A limited out-of-bounds memory read in the host-facing BMC firmware management service of IBM OpenBMC can be triggered by a host system to crash that service and read a small amount of BMC internal memory, producing low confidentiality and availability impact (CVSS 3.4). Only agents who already hold high-privileged control of the managed host can reach the vulnerable interface, since the flaw sits on the local host-to-BMC path (AV:L, PR:H) rather than on the network. Affected firmware levels are FW1060.00 through FW1060.81, FW1110.00 through FW1110.31, and FW1120.00 through FW1120.01; there is no public exploit code identified and no confirmed active exploitation (not in CISA KEV), so the practical risk is low and is largely contingent on the host already being compromised at a privileged level.
CVE-2026-6103 is an as-yet uncharacterized security issue in software distributed and maintained through Ubuntu, reported to this pipeline solely by the Ubuntu vendor feed with no accompanying description, CVSS vector, or CWE classification. Because the report carries no affected package name, no version range, and no attack-vector metadata, it is not possible to state who is affected beyond Ubuntu users of whatever component the Ubuntu Security Tracker assigns to this CVE, or what an attacker could achieve. No public exploit identified at time of analysis, no CISA KEV entry is present, and no EPSS score was supplied; risk cannot be meaningfully assessed from the available data until the Ubuntu Security Tracker entry (and the corresponding NVD record) is retrieved.
Local users with only low-level privileges on IBM i systems running Db2 Mirror for i 7.4, 7.5, or 7.6 can obtain partial sensitive information because the product encrypts data using AES in Electronic Codebook (ECB) mode, a deterministic cipher mode that leaks patterns in the underlying plaintext. The exposure is limited to confidentiality (C:L) with no integrity or availability impact, and exploitation requires local access plus the ability to observe data produced by the affected encryption code path, giving a low overall severity of 3.3. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (CISA KEV); no EPSS probability was supplied, consistent with a low-priority informational-disclosure weakness.
Hypervisor memory disclosure in IBM PowerVM firmware (FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81) allows an attacker who already holds root inside a guest partition to read a limited, non-attacker-controlled portion of uninitialized hypervisor memory through a hypervisor call interface, potentially exposing sensitive data belonging to the hypervisor or to co-resident guest partitions. According to the assessed CVSS vector (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N), exploitation requires local access and high privileges (root in a guest) and yields only a confidentiality impact of low severity, with no integrity or availability effect and no attacker control over which memory contents are returned. There is no public exploit code identified and no confirmed active exploitation (not listed in CISA KEV); the practical risk is concentrated in multi-tenant environments where untrusted parties run arbitrary guest OS images on shared Power hardware, while single-tenant systems face little exposure.
An entropy/random-generator failure on an Mbed TLS TLS 1.3 server (versions 3.2.0 through 3.6.6 and 4.0.0 through 4.1.0) can allow bytes to be removed from or injected into the beginning of the TLS stream, degrading integrity of the protected channel. The attack is not a normal network exploit: the prerequisite is that the attacker can first induce the server's entropy source to fail (for example via fault injection, RNG degradation, or resource exhaustion), which is why the issue is scored CVSS 2.9 (AV:L/AC:H) with integrity-only impact and no effect on confidentiality or availability. Only TLS 1.3 servers are affected - TLS 1.2 servers and client-side roles are out of scope - and no public exploit code or active exploitation has been identified at time of analysis.
Path traversal in the littrs Rust sandboxing library (versions 0.6.1 and 0.6.2) allows the `relative` argument passed to `Sandbox::mount` in crates/littrs/src/lib.rs to escape the intended sandbox mount point and reach files outside it. The flaw is not directly reachable by anonymous internet users: it requires an application built on littrs that routes attacker-influenced input into the mount path, and the independent assessment rates the attack vector as local with low privileges required (CVSS:3.1 AV:L/AC:L/PR:L/UI:N, C:L/I:L/A:L), even though the CNA's CVSS 4.0 vector (AV:N, CVSS 2.1) frames it as remotely performable. Publicly available exploit code exists, and the vendor was contacted but did not respond; no fixed release has been published, so risk is confined to deployments that actually feed untrusted values into `Sandbox::mount`.
Cross-site scripting in RuoYi-Vue-Pro (all versions up to 2026.08) allows remote attackers to inject script through the File Upload component implemented in yudao-module-infra/src/main/java/cn/iocoder/yudao/module/infra/controller/admin/file/FileController.java, which is later rendered in the administrative interface without adequate output encoding. Publicly available exploit code exists and the vendor was contacted but did not respond, so no vendor patch is available at time of analysis. Exploitation requires a victim to view the malicious file content (UI:P) and, per our independent assessment, realistically also depends on access to the upload endpoint and an authenticated user viewing the affected admin pages, keeping the practical severity in line with the CVSS 5.3 base score.
Open redirect in the Yudao (ruoyi-vue-pro) OAuth2 client component, affecting releases up to 2026.08, lets remote attackers manipulate the redirect_uri argument handled by validOAuthClientFromCache in OAuth2ClientServiceImpl.java so that a victim is bounced to an attacker-controlled site after clearing the authorization flow. No authentication is required (CVSS:4.0 PR:N), but the attack is not autonomous - it needs a victim to click a crafted authorization link and complete the flow (UI:P), and impact is limited to integrity-only redirection with no data disclosure or code execution. Publicly available exploit code exists and the vendor was contacted but never responded, so no vendor patch is confirmed; the independent assessment rates this a genuine but modest issue (CVSS:3.1 5.3, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N).
Server-side request forgery in the AI Knowledge Module of ruoyi-vue-pro (versions through 2026.08) allows an authenticated low-privilege user to coerce the application server into issuing arbitrary outbound HTTP requests via the AiKnowledgeDocumentServiceImpl.readUrl document-import function, which fetches a caller-supplied URL without adequate validation. Exploitation is remote and low-complexity and requires only a valid low-privilege account plus an enabled/reachable AI Knowledge feature; the practical impact is bounded by what the server can reach on the internal network, such as internal HTTP services, admin panels, or cloud instance-metadata endpoints, resulting in limited confidentiality and integrity exposure. Publicly available exploit code exists, no CISA KEV entry confirms active exploitation, and the vendor was contacted about the disclosure but did not respond, so an upstream patch is not available and this is a genuine but moderate-priority issue whose real-world severity depends on the operator's outbound egress controls.
Authenticated path traversal in the ruoyi-vue-pro (Yudao) WeChat MP material-upload component lets a low-privileged user write files outside the intended upload directory by embedding '../' sequences in a multipart filename passed to getOriginalFilename() in MpMaterialServiceImpl. Versions up to and including the 2026.08 release are affected whenever the yudao-module-mp module is deployed; the CVSS 4.0 base score is 2.1 (our independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, i.e. remote but requiring a valid account, with limited integrity impact only). Publicly available exploit code exists per the disclosing researcher, and the vendor was contacted but did not respond, so no vendor-released patch is identified at time of analysis.
SQL injection in the GoView data-visualization component of ruoyi-vue-pro (Yudao) lets an authenticated low-privilege user inject arbitrary SQL through the report data endpoint, exposing or altering backend database contents. The flaw sits in GoViewDataServiceImpl.getDataBySQL, which passes a user-controlled 'sql' argument into a query, and it affects deployments up through the 2026.08 release where the yudao-module-report / GoView module is enabled and reachable. Publicly available exploit code exists and the vendor was contacted but did not respond, so no vendor-released patch was identified at time of analysis; the base score is modest (5.3 under CVSS 4.0, PR:L, E:P) but the confidentiality impact is assessed as high, and there is no evidence of confirmed active exploitation (CISA KEV).
Cross-site scripting in Excalidraw 0.18.1 and earlier allows an attacker to embed an HTML/script payload in the customData.generationData.html field of a crafted scene file, which runs in the victim's browser origin when that file is imported through the restore.ts import handler. The issue is remotely reachable and unauthenticated (PR:N), but the attacker cannot trigger execution without the victim opening or importing the malicious file (UI:P), and publicly available exploit code exists with no indication of active exploitation in CISA KEV. Under the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N the impact is confined to client-side script execution with low confidentiality and integrity effects, making this a low-severity, high-caveat issue rather than a critical one.
In the Linux kernel, the following vulnerability has been resolved: mm/secretmem: properly account locked pages secretmem accounts folios by treating memory as if it were mlock()'d and thus limited by the RLIMIT_MEMLOCK limit. However the folios are unevictable and remain so until the inode is evicted, eliminating usual mlock() semantics - mapping folios then unmapping them does not clear their unevictable state, since it depends on AS_UNEVICTABLE, not PG_mlocked. A user can therefore easily work around the RLIMIT_MEMLOCK limit - simply map then unmap and VmLck no longer counts the secretmem range. Worse, folios are not accounted in the process's RSS, meaning the OOM killer won't know to kill the process. Repeatedly mapping/unmapping (or forking) can then result in the consumption of all available system memory with unevictable folios and cause system instability. A secretmem fd can be passed between processes and over fork so a per-process limit simply does not make sense, so follow the precedent set by io_uring, perf, skbuff, iommufd and xdp by tracking the number of locked pages in user_struct->locked_vm. Since the scope tracked is actually inode lifetime, the RLIMIT_MEMLOCK applies per-user not per-process, so it doesn't make sense to bypass for users with CAP_IPC_LOCK, therefore remove this bypass. There is simply no reason to carry on marking the mapping as mlock()'d since it's misleading and the lifecycle is now correctly handled, so remove this too. Note that secretmem does not support any form of truncation (including hole punching) and the folios are unreclaimable, so the folios need only be accounted on fault and unaccounted on inode destruction. __secretmem_account_pages() is more or less a duplicate of the code that io_uring etc. use, but since this is a bug fix that needs backporting, defer any de-duplication efforts to a follow-up. test_mlock_limit() asserts mlock_future_ok() on mmap(), however this has been removed, so remove the test altogether for the fix. A new test will be sent separately for upstream.