NoSQL injection in the @langchain/mongodb provider (part of langchainjs) before version 1.3.1 lets an authenticated low-privilege user read, modify, or delete another user's stored conversation history when multiple users' chat histories live in a shared MongoDB collection and the application passes an untrusted, attacker-controllable structured sessionId into MongoDBChatMessageHistory. The root cause is that the documented string type for sessionId is only enforced by TypeScript at compile time and is erased at runtime, so a value such as {$regex: "^victim-"} is handed straight into the MongoDB query filter and interpreted as a query operator rather than a literal identifier. Impact is tightly gated: applications that derive sessionId from an authenticated, server-controlled string (the documented correct usage) or that isolate histories per user are not affected, and no public exploit code was identified at time of analysis, with no confirmed active exploitation (CISA KEV).
Information disclosure in Google Chrome on iOS before version 155.0.8059.39 allows a remote, unauthenticated attacker to obtain sensitive information by supplying crafted network traffic to the browser's mobile input-validation path. Exploitation requires no user interaction but is constrained by high attack complexity - success depends on specific memory or timing conditions rather than a deterministic request - and the impact is limited to confidentiality with no code execution, integrity, or availability effect. There is no public exploit identified at time of analysis, and no evidence of active exploitation. Google rates Chromium security severity Medium (CVSS 5.9), and a vendor patch is available.
Missing authorization in the Chromoting (Chrome Remote Desktop) component of Google Chrome on Windows prior to 155.0.8059.39 lets a remote, unauthenticated attacker obtain sensitive information by sending crafted network traffic to a remoting endpoint. The flaw carries a CVSS 3.1 base score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), meaning no credentials or user interaction are needed but successful exploitation is gated by conditions the attacker cannot fully control; there is no public exploit identified at time of analysis. Exposure is limited to hosts that actually have the Chromoting/Chrome Remote Desktop functionality in use, and Google has shipped a fixed build rated Medium severity.
Denial of service in SSSD (the System Security Services Daemon) allows remote unauthenticated attackers to crash the daemon by presenting a certificate that is missing the expected Security Identifier (SID) extension during authentication or lookup operations. Only deployments explicitly configured with SID-based certificate mapping rules reach the vulnerable code path, since the certificate-to-user lookup logic dereferences the SID extension without first confirming it exists; standard installations that do not use SID-based certificate mapping are not affected. The flaw is rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/C:N/I:N/A:H, availability-only) and, per available intelligence, no public exploit code exists and exploitation has not been confirmed as active - no public exploit identified at time of analysis.
Incorrect authorization in Google Chrome's Sync feature (all versions prior to 155.0.8059.39) allows a remote, unauthenticated attacker to obtain sensitive synced information via crafted network traffic, although the High attack complexity rating indicates the attacker must satisfy conditions outside their control rather than reliably triggering the flaw on demand. Only users with Chrome Sync enabled are meaningfully exposed, and impact is limited to confidentiality disclosure of synced data with no code execution, tampering, or denial of service. No public exploit code has been identified at time of analysis, CISA's SSVC framework records no known exploitation, and a vendor patch is available.
Incorrect authorization in Google Chrome's built-in PDF handling on Android (versions prior to 155.0.8059.39) allows a malicious application already co-installed on the same device to obtain sensitive information after the victim is socially engineered into interacting with a crafted PDF. The issue is unauthenticated from a credentials standpoint (CVSS PR:N) but is effectively local in nature: it cannot be triggered purely remotely, it depends on the attacker first getting a separate app onto the device, it requires victim interaction, and its impact is confined to confidentiality with no integrity or availability effect. No public exploit code has been identified at time of analysis, CISA SSVC records Exploitation=none and Automatable=no, and Chromium rates the issue Medium severity; the signals point to a genuine but low-urgency issue rather than a top priority, though a vendor patch is available and should be applied through normal update cycles.
Defense-in-depth bypass in Coraza WAF 3.4.0 through 3.7.0 causes the multipart body processor to silently swallow io.ErrUnexpectedEOF, so a truncated multipart/form-data request neither sets MULTIPART_STRICT_ERROR nor returns a request-body error, and the two canonical defensive rules shipped in coraza.conf-recommended (200003 MULTIPART_STRICT_ERROR and 200002 REQBODY_ERROR) fail open. Remote unauthenticated attackers (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N, 5.8) can send a body that omits the closing boundary or cuts off mid-part and have it processed as if well-formed, neutralizing the parser-disagreement catch-all and enabling multipart smuggling or CRS evasion chains against backends whose multipart parser disagrees with Go's mime/multipart reader. No active exploitation is confirmed (not in CISA KEV), though the vendor advisory publishes a working reproduction proof-of-concept and the vendor-released fix is v3.8.0.
Remote, unauthenticated log-injection in Coraza WAF's Native audit-log formatter (all releases 3.0.0 through 3.7.0) allows any client whose data lands in an audit-log field - most easily the request body - to embed CR and LF bytes that forge new section boundaries and complete fake log entries inside a defender's audit log. The impact is integrity-only (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N, score 5.8): an attacker can shift attribution to a spoofed client IP, split SIEM correlation by fabricating boundary lines, poison line-based grep/awk/tail pipelines, or bury a genuine rule match under attacker-controlled noise. No confirmed active exploitation (not listed in CISA KEV), but the upstream GHSA advisory publishes a reproducible proof-of-concept request, and the fix shipped in v3.8.0.
SSSD's NFS idmap plugin contains an out-of-bounds write (CWE-787): when a cached user or group name is larger than the destination buffer it is copied into, the size check fires but the copy proceeds anyway. An authenticated, low-privileged local attacker can request identity lookups that resolve to such oversized cached entries, crashing the identity-mapping service (denial of service) and potentially corrupting adjacent process memory; the attack is local-only and depends on the oversized-cache precondition, giving it high attack complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H, 5.8). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Server-side request forgery in the agent import functionality of Amazon Bedrock AgentCore Starter Toolkit versions before 0.3.14 allows an authenticated actor within the same AWS account to make the environment of a user importing a Bedrock Agent issue arbitrary outbound requests and read arbitrary local files. The attacker must supply crafted external reference values in the OpenAPI content associated with a Bedrock Agent action group, and exploitation requires the victim to actively import that agent; this narrow interaction requirement and the same-account authentication prerequisite limit the practical exposure, consistent with the vendor's Medium (CVSS 4.0 5.7) rating and our assessed CVSS 3.1 score of AV:N/AC:L/PR:L/UI:R with high confidentiality impact only. No public exploit code has been identified at time of analysis, and no known active exploitation has been reported.
CVE-2026-55480 is currently recorded only against Ubuntu Linux, with the sole intelligence signal being that the entry was reported by vendor:ubuntu, meaning Canonical's security team is the originating source for the record. The supplied data contains no description, no CVSS score or vector, no CWE classification, no CPE strings, and no version ranges, so the specific component, attack vector, authentication requirement, and impact cannot be characterized at this time. No public exploit code has been identified at time of analysis, and no CISA KEV listing is present, but this reflects the absence of data rather than a confirmed negative - defenders should treat the entry as unassessed and pull the authoritative record from the Ubuntu CVE tracker and NVD before drawing any risk conclusion.
RabbitMQ Java Client library releases prior to 5.35.0 can leak plaintext broker credentials because ConnectionFactoryConfigurator.load() wraps AMQP URI parsing failures in IllegalArgumentException messages that contain the raw amqp://user:pass@host URI. Any application that supplies credentials inside the connection URI and then hits a setup error - malformed URI syntax or a TLS NoSuchAlgorithmException/KeyManagementException - will write those credentials into startup logs, APM dashboards, CI output, or copied stack traces, where users without broker access may read them. This is a genuine but low-urgency credential-disclosure issue rather than a widely-exploitable critical flaw: exploitation is passive and conditional, requires the attacker to already have read access to the log sink, and only affects the configurator load() path where credentials are embedded in the URI. No public exploit identified at time of analysis; the vulnerable behavior is fixed in version 5.35.0, and the CVSS 4.0 score of 5.7 (AV:L/AC:L/AT:P/PR:L, VC:H) reflects that local, low-privilege, log-reading access with specific preconditions is needed.
CRI-O instances explicitly configured with a non-empty bind_mount_prefix can be induced to resolve a container's CRI hostPath bind-mount source outside the intended prefixed root, giving an attacker with the ability to define such mounts read and write access to host files and a route to privilege escalation. The flaw is conditional rather than broadly exploitable: it requires the non-default bind_mount_prefix setting, high privileges to specify hostPath mounts (PR:H), and a carefully arranged intermediate absolute symlink in the requested path (AC:H), and default-configured CRI-O deployments are not exposed. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so this is a moderate, conditional risk rather than an urgent priority.
Local information disclosure in Dell Command | Configure (DCC) versions prior to 5.2.3.35 stems from a hard-coded cryptographic key embedded in the product, allowing an unauthenticated attacker with local access (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 6.2) to recover that key and decrypt data protected with it. There is no integrity or availability impact, and remote network exploitation is not possible - the attacker must already have a local presence on the endpoint, so realistic exposure is confined to insider scenarios, post-compromise footholds, or shared/multi-user Dell workstations. No public exploit code or confirmed active exploitation was identified in the available intelligence at time of analysis, and the primary limiting factor remains the mandatory local access requirement; Dell published advisory DSA-2026-378 covering this and other issues in the same release.
A local, authenticated user on hosts running sssd (System Security Services Daemon) can stall the daemon's responder service by opening and holding a large number of concurrent connections to a responder socket while continuing to queue new connection attempts, driving the responder past its file-descriptor limit into an unthrottled retry loop. The result is a denial-of-service condition with high CPU consumption that blocks legitimate identity and authentication lookups (NSS/PAM) for other users. Exploitation requires local access and is rated high complexity (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H, base 4.7), so realistic exposure is concentrated on shared or multi-user systems rather than single-administrator hosts; there is no public exploit identified at time of analysis and no confirmed active exploitation (no CISA KEV listing).
Out-of-bounds read in NVIDIA TensorRT can crash the inference runtime when an application parses an attacker-supplied, maliciously crafted model or serialized engine file, yielding denial of service limited to the affected process. The flaw is rated CVSS 5.5 (CWE-125, AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), meaning it is not remotely reachable: a local user or local process must deliberately load the crafted input, and no privileges are required (PR:N) although user interaction is (UI:R). There is no privilege escalation or confirmed data exposure from this vector, no public exploit identified at time of analysis, and it is not listed in CISA KEV; consistent with our assessment this is a moderate-severity, low-urgency issue best handled through routine patching and supply-chain hygiene around model/engine files.
A local, low-privilege attacker can crash the SSSD PAM responder on Red Hat Enterprise Linux (versions 6 through 10) and Red Hat OpenShift Container Platform 4 by sending a crafted PAM request that contains a zero-length authentication token. The flaw, tracked as CVE-2026-104042 with a CVSS score of 5.5, stems from missing length validation that leads to an out-of-bounds read and a denial of service; it requires an existing local account and no user interaction. No public exploit code has been identified at time of analysis, and this is a moderate-severity local DoS rather than a remote or privilege-escalation issue.
Information disclosure in the HPE Networking ClearPass Policy Manager client software allows a locally positioned attacker holding a low-privilege account or session on the host to read sensitive information that the client handles or stores. The flaw is constrained by its access prerequisites: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N confirms that exploitation requires local presence with some existing privilege, cannot be triggered remotely or by an unauthenticated actor, and needs no user interaction, while integrity and availability are unaffected and only confidentiality is impacted. Exploitation is rated moderate (CVSS 5.5), no public exploit code has been identified at time of analysis, and there is no evidence of confirmed active exploitation (no CISA KEV listing), so the practical risk is dominated by the need for an attacker to already be resident on the target machine with a valid low-privileged foothold; this is not a remote, unauthenticated compromise vector.
Plaintext storage of a password by Dell Command | Configure (DCC) in versions prior to 5.2.3.35 allows a low-privileged local user to read that credential and disclose it, rated CVSS 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N). This is a moderate-severity, low-urgency issue: the attacker must already hold an authenticated local account on a Dell commercial-class endpoint with DCC installed, and the impact is confined to information disclosure with no integrity or availability loss. There is no remote attack path, no public exploit identified at time of analysis, and no CISA KEV listing; the vendor has published a fixed build, 5.2.3.35, in Dell security advisory DSA-2026-378.
A local denial of service in SSSD's Name Service Switch (NSS) responder lets an attacker who can reach the responder's UNIX socket crash the name-resolution service by sending a crafted request containing an undersized packet header, which causes an integer underflow followed by an out-of-bounds read during packet parsing. Affected deployments are Red Hat Enterprise Linux 6, 7, 8, 9, and 10, plus Red Hat OpenShift Container Platform 4 nodes running SSSD. The impact is availability-only (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), exploitation requires prior local access and socket reachability, and no public exploit identified at time of analysis.
Unprivileged local users can exhaust memory in the SSSD NSS responder by repeatedly requesting lookups for nonexistent entries, causing denial of service on Red Hat Enterprise Linux 6 through 10 and Red Hat OpenShift Container Platform 4. The negative cache in SSSD lacks a bound on total stored entries and only evicts expired records when an existing key is rechecked, so the cache grows until the responder becomes unresponsive or terminates. This is a local, availability-only issue requiring an authenticated account (CVSS 5.5, PR:L); no public exploit code or active exploitation is identified at time of analysis.
Denial of service in SSSD's autofs responder allows a local attacker with an existing account on the host to crash the responder process by writing a specially crafted request containing an invalid packet length to its UNIX domain socket. The malformed length triggers an integer underflow that produces an out-of-bounds read (CWE-125), terminating the responder and disrupting automount map lookups; there is no confidentiality or integrity impact and no remote vector. Exploitation requires the autofs responder to be enabled in sssd.conf and local reachability of its socket (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 5.5); no public exploit code and no confirmed active exploitation were identified at time of analysis. Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 (via packaged SSSD) are listed as affected.
Local denial of service in the SSSD Kerberos Credential Manager (KCM) responder allows an authenticated local user to exhaust host memory and make the service unresponsive by holding a persistent connection open while repeatedly storing and destroying Kerberos credentials. The flaw is a resource-lifecycle defect (CWE-772): cached objects are not released when credentials are removed, so memory grows monotonically until the responder stalls. Exploitation requires a valid local account and sustained store-then-destroy activity, yields availability impact only (CVSS 5.5, AV:L/PR:L/UI:N/A:H), and does not provide code execution or privilege escalation; no public exploit code or confirmed active exploitation was identified at time of analysis, and systems that do not use the KCM responder are not affected.
Denial of service in SSSD's autofs responder allows an authenticated local unprivileged user to repeatedly request master automount map updates, triggering global cache invalidation and forcing repeated backend directory lookups, which degrades automount availability and elevates resource consumption. Affects Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 when SSSD-backed automount maps are served from a backend directory provider such as LDAP or Active Directory. This is a moderate-priority local availability issue (CVSS 5.5) with no public exploit code identified at time of analysis.
Memory exhaustion in the SSSD autofs responder can let a local, authenticated unprivileged user deny service on affected hosts by holding an open client connection while repeatedly submitting valid requests, since per-request memory is only reclaimed when the connection closes. The flaw affects SSSD deployments on Red Hat Enterprise Linux 6 through 10 and Red Hat OpenShift Container Platform 4, but the vulnerable code path is only reachable when the autofs responder is explicitly enabled in sssd.conf - a non-default configuration. Exploitation is limited to local access (AV:L/PR:L) with no impact on confidentiality or integrity, so it is correctly rated medium (CVSS 5.5); no CISA KEV entry and no public exploit code have been identified at time of analysis, and a realistic impact generally requires a shared, multi-user host where one user's resource consumption degrades service for others.
UI misrepresentation in Google Chrome's File System Access (FileSystem) component affects browser builds prior to 155.0.8059.39, where a remote, unauthenticated attacker can use social engineering to trick a user into granting file access through a spoofed or misleading interface element, bypassing intended system access restrictions. Successful exploitation is limited to low confidentiality and low availability impact with no integrity effect (CVSS 5.4, CWE-451), and depends entirely on victim interaction: the user must first be lured to a crafted HTML page and then engage with the misrepresented prompt. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); the vendor has shipped a fixed release, so exposure is largely confined to users running outdated, non-auto-updated Chrome installations.
Address bar spoofing in Google Chrome for iOS before 155.0.8059.39 lets a remote, unauthenticated attacker make a crafted HTML page appear to originate from a trusted site, enabling phishing and possible disclosure of information the victim enters. Exploitation requires the victim to be socially engineered into opening the page (CVSS 5.4, medium; assessed impact limited to confidentiality, with no integrity or availability effect), and CISA's SSVC assessment records exploitation as none and automation as no, so large-scale automated abuse is unlikely. No public exploit code has been identified at time of analysis, and the vendor has shipped a fix in Chrome 155.0.8059.39.
Unauthorized data stream modification in Elasticsearch allows an authenticated user who holds privileges over only a single resource to alter data streams outside their authorized scope through the Modify Data Streams API, enabling data injection into those streams or degrading their searchability. The flaw is rated CVSS 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L) and is confined to integrity and availability - it explicitly does not let the attacker read a data stream they could not already access. Only deployments running 7.17.5-7.17.29, 8.2.2-8.19.18, 9.0.0-9.3.7, or 9.4.0-9.4.3 are affected, and there is no public exploit identified at time of analysis; the vendor security update (ESA-2026-188) points to fixed releases 8.19.19, 9.3.8, and 9.4.4.
UI misrepresentation in Google Chrome's WebAppInstalls flow - every build prior to 155.0.8059.39 - allows remote, unauthenticated attackers to spoof browser interface elements by luring a victim to a crafted HTML page and having them interact with the Web App installation prompt. The outcome is user deception rather than code execution or data theft, and exploitation is gated by mandatory user interaction (UI:R): the victim must both load the attacker's page and engage with the affected UI flow. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment rates exploitation as "none" with Automatable: no; Google rates this a Chromium security severity Low, and while the published base score of 5.4 appears mid-range, the social-engineering dependency, the deception-only payoff (integrity of what the UI communicates, not confidentiality or availability loss), and automatic delivery of the fix through Chrome's update channel keep real-world risk genuinely low.
UI spoofing in Google Chrome before 155.0.8059.39 allows remote, unauthenticated attackers to misrepresent browser interface elements to a victim by luring them to a crafted HTML page, with the attacker explicitly relying on social engineering to make the deception convincing. The flaw carries a medium-severity CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L), and exploitation requires the user to visit an attacker-controlled or compromised page and then trust and act on the fabricated UI; no authentication is needed (PR:N) and the underlying flaw is not automatable, so SSVC rates technical impact as partial. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, though a vendor patch is available.
UI spoofing in Google Chrome versions prior to 155.0.8059.39 lets unauthenticated remote attackers misrepresent browser interface elements through a crafted HTML page, but successful exploitation requires the victim to actively load that page. The flaw is limited to user-interface deception (CWE-451) with low confidentiality impact, and no public exploit code or active exploitation has been identified at time of analysis; CISA SSVC rates exploitation as none and automation as not possible. This is a low-priority issue despite the network attack vector.
UI spoofing in Google Chrome's Web Authentication (Passkeys & Security Keys) component allows remote attackers to render deceptive interface elements to users who open a crafted HTML page, because the browser fails to enforce an authorization check before displaying WebAuthn-related UI. The flaw affects Google Chrome on all platforms prior to 155.0.8059.39 and carries a moderate 5.4 CVSS score, although Chromium's own security severity rating is Low and the outcome is limited to user-interface deception rather than code execution or credential exfiltration. No public exploit code has been identified at time of analysis, there is no CISA KEV listing, and the attack is only reachable through mandatory user interaction (CVSS UI:R) with no authentication or privileges required (PR:N). Google has released a patched build, and all exploitation signals converge on a low real-world priority.
Clickjacking in the EVP component of Google Chrome allows a remote, unauthenticated attacker to overlay and spoof UI elements by tricking a victim into visiting a crafted HTML page and clicking on concealed controls. The attack is purely a UI-redressing/deception issue - the independent assessment scores it as no confidentiality, no availability, and low integrity impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) despite the vendor's 5.4 'Medium' rating - and it succeeds only where social engineering works, with no code execution or data exfiltration. Google shipped a fix in Chrome 155.0.8059.39; no KEV listing and no public exploit code identified at time of analysis.
Web origin policy bypass in Google Chrome on Android lets unauthenticated remote attackers cross same-origin boundaries by inducing a victim to open a crafted HTML page that is rendered through the CustomTabs feature, in releases prior to 155.0.8059.39. Exploitation requires user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) and yields only partial confidentiality and integrity impact with no availability effect and no scope change, so this is a moderate, not top-tier, priority. No public exploit code has been identified at time of analysis and EPSS is low at 0.20% (9th percentile), though the vendor has shipped a fixed Chrome release and Chromium rates the issue High severity on its internal scale.
UI spoofing in the Chromoting (Chrome Remote Desktop) component of Google Chrome on Windows prior to 155.0.8059.39 lets an unauthenticated remote attacker misrepresent interface elements to a victim, but only after the user has been socially engineered into interacting with crafted network traffic. The attack cannot succeed silently: it requires the victim to be actively using Chromoting while the crafted traffic is delivered, and it yields at most limited information exposure - our assessment scores it CVSS 5.4 with low confidentiality impact and no integrity or availability impact. No public exploit was identified at time of analysis, and Google has addressed the flaw in 155.0.8059.39, so this is a low-priority issue for environments that keep Chrome current on the stable update channel.
Authentication bypass in SSSD permits a user with valid credentials for an already-expired account to authenticate to the system when SSSD is configured to enforce account expiration using LDAP shadow attributes and the expiration value is stored as zero. This moderate-severity logic flaw (CVSS 5.4, CWE-193) affects Red Hat Enterprise Linux 6, 7, 8, 9, and 10, as well as Red Hat OpenShift Container Platform 4; exploitation requires the non-default shadowExpire=0 configuration and valid credentials for the expired account. No public exploit code or active exploitation has been identified at time of analysis.
Missing authorization in Google Chrome before 155.0.8059.39 allows a remote attacker to bypass system access restrictions by luring a victim to a crafted HTML page, with only partial confidentiality and integrity impact. No public exploit identified at time of analysis, the EPSS score is 0.19% (8th percentile), and CISA's SSVC assessment records no exploitation; the vendor has released a patched version.
Authentication bypass in Keycloak's OIDC Device Authorization Grant flow allows an attacker who already possesses a valid user password to evade a client's configured minimum authentication level, including mandatory multi-factor authentication, and gain unauthorized access to the Keycloak Admin REST API, according to Red Hat. The flaw is a missing enforcement check (CWE-287) affecting Red Hat Build of Keycloak and Red Hat Single Sign-On 7 deployments where the device authorization flow is enabled for a client that requires elevated authentication. Exploitation requires prior credential compromise (CVSS PR:L) and the targeted client must actually mandate MFA or another authentication level; no public exploit code or CISA KEV active exploitation is identified in the available data, and EPSS is not provided. The CVSS score is 5.4 (moderate), with limited confidentiality and integrity impact.
UI spoofing in Google Chrome desktop builds prior to 155.0.8059.39 allows a remote attacker to misrepresent browser UI elements to a victim through a crafted HTML page, potentially deceiving the user into trusting content that does not correspond to the real page or origin. Exploitation is not passive: it requires the victim to visit the attacker-controlled page and then be successfully manipulated via social engineering, which is why the independent assessment scores the vector as AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N - a low-integrity-only impact with no confidentiality or availability loss. No public exploit code or active exploitation has been identified at time of analysis, CISA's SSVC framework rates exploitation as none and automatable as no with only partial technical impact, and vendor-released patches are available in Chrome 155.0.8059.39.
UI misrepresentation in Google Chrome's WebAppInstalls (progressive web app / web app install) flow in builds prior to 155.0.8059.39 lets a remote, unauthenticated attacker bypass system access restrictions by luring a victim to a crafted HTML page and inducing them to approve a deceptive install prompt. The attack is entirely gated by user interaction and social engineering (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L), with impact limited to Low confidentiality and availability and no integrity loss, and Google/Chromium rates the underlying issue Low security severity. No public exploit code was identified at time of analysis and the flaw is not confirmed as actively exploited (CISA KEV); this is a low-priority issue where patching is straightforward and the practical risk depends on user behaviour rather than on any remotely triggerable primitive.
Missing authorization checks in Chrome's Permissions component (all versions prior to 155.0.8059.39 on desktop) allow a remote attacker to bypass system access restrictions, but only after first compromising the renderer process and inducing the victim to interact with a crafted HTML page. This is a sandbox/permission-boundary bypass, not an initial-access or remote-code-execution flaw: exploitation requires a separate prior-stage renderer compromise plus social engineering, and impact is capped at limited confidentiality and integrity loss with no availability impact and no scope change. Google has shipped a fix in Chrome 155.0.8059.39, EPSS is low at 0.19% (8th percentile), no public exploit code was identified at time of analysis, and CISA's SSVC framework rates exploitation as 'none' with automation as 'no'.
Code injection in the Extensions subsystem of Google Chrome prior to 155.0.8059.39 lets a remote attacker spoof browser UI elements once a victim has been socially engineered into installing a crafted extension. Exploitation is gated behind mandatory user interaction (UI:R) and the deliberate addition of attacker-controlled extension code, so exposure is limited to users who sideload or approve an untrusted extension rather than to any default, clean Chrome install; there is no public exploit identified at time of analysis. Google has shipped a fix in the Chrome 155.0.8059.39 stable channel release, and the issue is rated Medium at 5.4 with only low confidentiality and low availability impact.
UI misrepresentation in Google Chrome's PermissionElement allows remote attackers to spoof browser-rendered permission UI through a crafted HTML page, deceiving a user who visits that page into acting on a false prompt; the assessed impact is limited to low confidentiality (C:L/I:N/A:N) with no integrity or availability impact. The issue is unauthenticated at the network layer (PR:N) but requires the victim to both load the attacker's page and be successfully social-engineered by the spoofed interface (UI:R), so exploitation is not automatable (SSVC Automatable: no). No public exploit code has been identified and there is no evidence of active exploitation (not in CISA KEV); Google has released a fixed build, Chrome 155.0.8059.39, so this is a genuine but low-priority issue.
Google Chrome versions before 155.0.8059.39 contain an improper input validation flaw in the WebAudio implementation that can let an attacker who has already compromised the renderer process bypass system access restrictions via a crafted HTML page. The independent assessment scores this as low real-world priority (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N): the required prior renderer compromise is the dominant limiting factor, making it a second-stage or sandbox-escape building block rather than a standalone remote attack. No public exploit has been identified at time of analysis, CISA SSVC reports Exploitation: none, and EPSS is 0.18% (7th percentile), so patching should follow routine Chrome update cycles.
Improper input validation in the Omnibox of Google Chrome for Android prior to 155.0.8059.39 lets a remote attacker bypass web origin policy using a crafted HTML page, a weakness rated High by Chromium's security team but only Moderate (CVSS 5.4) under the generalized rubric. The attack is unauthenticated (PR:N) but requires the victim to be socially engineered into opening the malicious page (UI:R), and the resulting impact is bounded to partial confidentiality and integrity exposure with no availability loss. No public exploit code has been identified at time of analysis, EPSS is low at roughly 0.18% (7th percentile), and there is no CISA KEV listing; exploitation is limited to Android builds below 155.0.8059.39 and a vendor patch is available.
Cross-site request forgery in the ReadingList feature of Google Chrome for Android (versions prior to 155.0.8059.39) allows a remote attacker to bypass web origin policy by social-engineering a victim into loading a crafted HTML page. Exploitation requires user interaction (UI:R) and is limited to the Android platform; no public exploit code has been identified and the EPSS score is low at 0.18% (7th percentile). Google has released a patched version (155.0.8059.39), and the issue is rated medium severity by Chromium.
Stored cross-site scripting in the Gitea container registry (versions through 1.27.3) lets any user with permission to push container images publish a blob whose manifest declares a text/html media type, which Gitea then serves back verbatim as the blob's Content-Type with no Content-Disposition header and no restrictive Content-Security-Policy - so the embedded JavaScript executes on the Gitea origin when an authenticated victim opens the blob URL. Impact is bounded but real: the attacker must already hold registry push rights and the victim must be induced to open the crafted URL directly, but success allows same-origin actions as the victim such as creating API tokens. The flaw is rated 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), carries EPSS 0.18% (7th percentile), shows CISA SSVC exploitation of 'none', and has no public exploit identified at time of analysis; exploitation requires an account with image-push permission (authenticated, PR:L) and victim interaction (UI:R).
UI spoofing in Google Chrome's WebAppInstalls component lets a remote, unauthenticated attacker mislead a victim with fabricated install-related browser UI on desktop builds prior to 155.0.8059.39. The root cause is incorrect authorization (CWE-863) in the web-app installation surface, and because the CVSS vector requires UI:R, the victim must actively navigate to an attacker-crafted HTML page before anything happens - so the realistic outcome is assistance to phishing or social engineering rather than code execution or credential theft. Chromium rates this Low severity (NVD base 5.4), our independent assessment further narrows the impact to low integrity only, there is no KEV listing indicating confirmed active exploitation, and no public exploit code has been identified at time of analysis.
Improper privilege management in the Chrome UI on macOS allows a remote attacker to bypass system access restrictions by socially engineering a victim into visiting and interacting with a crafted HTML page. Only Chrome for macOS builds prior to 155.0.8059.39 are affected; no authentication is required (PR:N), but the attack cannot succeed without the victim actively engaging with the malicious page (UI:R). Google rates the Chromium security severity as Low, EPSS is just 0.18% (7th percentile), SSVC records no exploitation and no automatable path, and no public exploit code has been identified at the time of analysis. Impact is limited to partial confidentiality and integrity loss with no availability effect.
Incorrect authorization in Google Chrome's PermissionElement component, affecting desktop builds prior to 155.0.8059.39, allows a remote attacker to bypass system access restrictions by enticing a user to load a crafted HTML page. The attacker needs no credentials and no prior access (CVSS:3.1/AV:N/AC:L/PR:N), but successful exploitation depends on the victim actively visiting or rendering the malicious page (UI:R) and on reaching the specific permission-handling code path, so impact is confined to partial confidentiality and integrity loss with no availability impact. Risk is low in practice: EPSS is 0.18% (7th percentile), there is no CISA KEV listing and no public exploit identified at time of analysis, CISA's SSVC rates exploitation as none and automatable as no, and Chromium itself rates the issue Low severity despite the 5.4 base score; vendor-released patches are available in version 155.0.8059.39.