Opening a crafted DVD or disc image in applications that use libdvdnav before 7.0.0 can trigger a heap out-of-bounds read during chapter enumeration and crash the application. The attacker supplies media whose VMGI title declares a vts_ttn larger than the corresponding title set's part-of-title entries; exploitation is local and requires the victim to open the crafted media, and only availability is affected. No public exploit has been identified at time of analysis, and the vendor has released a patch.
Opening a crafted DVD or disc image in a media player built on VideoLAN libdvdnav through 7.0.0 can crash the application through an out-of-bounds read in DVD navigation handling. The fault is triggered when the disc's First Play program chain issues a JumpTT command with title 0 or an oversized title number, causing the library to index past its heap title table because validation relies on an assert rather than a runtime bounds check. Exploitation requires local delivery and user playback of the malicious media, no public exploit was identified at time of analysis, and the assessed impact is denial of service only.
Divide-by-zero in libschroedinger (Schroedinger) through 1.0.11 allows local attackers to crash applications that decode a crafted Dirac stream, resulting in denial of service. The flaw is reached when a low-delay picture supplies a zero slice_bytes_denom or slice count, causing SIGFPE in schro_decoder_parse_transform_parameters and schro_decoder_parse_lowdelay_transform_data. Exploitation requires the victim to open or process a malicious media file (user interaction), and no public exploit code has been identified at time of analysis; impact is limited to availability.
Decoding a crafted low-delay Dirac stream with an out-of-range wavelet filter index (7 or greater) or transform depth (5 or 6) in libschroedinger through 1.0.11 triggers an out-of-bounds read past a static quantiser table, crashing the application. The flaw is availability-only (no code execution, data disclosure, or integrity impact) and requires local access plus user interaction to process the malicious stream; no public exploit was identified at time of analysis, and the issue is assessed as moderate severity.
Denial of service in OW2 ASM 9.11 before 9.11.1 occurs when a build tool, instrumenter, agent, or analyzer uses ClassReader.accept() to transform an attacker-supplied class whose rewritten method body grows beyond 65535 bytes; 16-bit forward-reference offsets truncate in Label.resolve() and cause an infinite loop that hangs the affected process. The issue is local (AV:L) and requires the victim to process a crafted class through a code-growing transformation path (UI:R), with impact limited to availability of that single process and no code execution or data disclosure. No public exploit code was identified at time of analysis and no CISA KEV entry is associated; the vendor addressed the flaw in ASM 9.11.1.
A crafted Microsoft Word .doc file can crash applications built on wvWare wv through 1.2.9 by triggering a heap-based out-of-bounds read in the wvGetSTSH stylesheet parser. The issue is local and requires the victim to open the malicious document; the assessed impact is availability-only, with no code execution or data disclosure established. No public exploit code or CISA KEV active exploitation was identified at time of analysis.
Stack-based out-of-bounds read in wvWare wv through 1.2.9 allows an unauthenticated local attacker to cause a client-side denial of service: a victim must open a crafted .doc file whose FKP structure carries an oversized crun value, triggering wvGetPAPX_FKP or wvGetCHPX_FKP to read past a 512-byte stack buffer and crash AbiWord or another libwv-based reader. The assessed impact is availability only (CVSS 4.0 local, UI:P, A:H; CVSS 3.1 local, UI:R, A:H), with no confidentiality or integrity impact established. No public exploit code or CISA KEV active exploitation was identified at time of analysis.
Path traversal in Vita3K builds before 4187 allows a crafted .vpk archive to write files outside the emulator's install directory, potentially leading to host code execution with the privileges of the Vita3K process. Exploitation is local and requires the victim to install a malicious package, so risk is moderate-to-low for most environments but non-trivial for users who routinely sideload .vpk files. No public exploit code has been identified at time of analysis, and the flaw is remediated in build 4187.
Code injection (CWE-94) in the HivePress WordPress plugin, affecting versions through 1.7.32, allows an authenticated user holding only low privileges to influence the generation of executable code on the host site, with the assessed impact falling entirely on confidentiality. Exploitation is network-reachable at low complexity with no user interaction, but it is gated by authentication (CVSS PR:L), so an attacker must first obtain a valid account on the target WordPress installation - fully unauthenticated visitors cannot exploit it. EPSS, CISA KEV, and public exploit-code status were not provided in the source data, so no active-exploitation signal can be asserted; the vendor's fix version is likewise not enumerated in the available input, and remediation details should be confirmed against the Patchstack advisory.
Authentication bypass in the VideoWhisper '2Way VideoCalls and Random Chat' WordPress plugin (webcam-2way-videochat) through version 6.1.5 lets remote attackers reach protected plugin functionality without valid credentials, yielding low confidentiality and integrity impact (CVSS 3.1 base 6.5, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). Because the vector shows no privileges and no user interaction, any network-reachable WordPress site with this plugin active is exposed, though the population at risk is limited to sites that deliberately installed this niche webcam/chat plugin. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.
Missing authorization in WPExperts Advanced File Manager through 5.4.14 allows network attackers to reach plugin actions that lack proper access-control checks, with limited integrity and availability impact and no confidentiality loss. The Patchstack advisory tags the issue as an authentication bypass; the published CVSS base is 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L), while the independent assessment rates it PR:L and cautions that realistic exploitation often requires a low-privileged authenticated WordPress account that can access the vulnerable handlers. No public exploit identified at time of analysis, and no CISA KEV active-exploitation confirmation was provided.
Missing authorization in the Kit (formerly ConvertKit) WordPress plugin through 3.4.6 lets unauthenticated remote attackers perform limited unauthorized reads and writes against plugin-managed data and functions. The flaw is a CWE-862 access-control gap rated CVSS 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), affecting default installations with no privileges or user interaction required. No public exploit identified at time of analysis.
Missing per-user authorization middleware on seven Gitea API routes lets any authenticated account holding an API token with read-user scope enumerate the followers, following list, starred and watched repositories, and public SSH/GPG keys of individual users whose profile is set to 'limited' or 'private' visibility, which should otherwise be hidden from them. It affects Gitea up to and including 1.27.2 and is fixed in 1.27.3 and 28.0.0, with the disclosure shipped alongside the 28.2.0 release; exploitation requires a valid account and token (PR:L) and only works against non-public users, so the practical impact is moderate information disclosure rather than a critical exposure. There is no CISA KEV listing and no public exploit identified at time of analysis, and EPSS is 0.16% (5th percentile), consistent with a low-urgency bug that is nonetheless trivially scriptable once an account is obtained.
Authenticated users on a Gitea instance can harvest private-profile information - full name, location, website, and free-text description - from other accounts by sending requests to the POST /{username} follow and unfollow endpoint, because the profile visibility check was applied only to GET requests while the POST handler merely required a signed-in session. Anyone holding a valid account on Gitea 1.22.0 through 28.0.0 (self-registration, where enabled, is enough) can pull these fields from the response for any target whose profile visibility is set to private; public profiles expose nothing new. The vendor fixed the flaw in 28.1.0 and disclosed it alongside the 28.2.0 release; there is no public exploit code identified at time of analysis, it is not in CISA KEV, and EPSS is low at roughly 0.16% (4th percentile), so this is a genuine but modest-priority information-disclosure issue.
Memory exhaustion in Gitea's Actions artifact v4 (Twirp) service lets an authenticated user who can run a workflow crash the server process by sending an oversized request body to the artifact handlers. The handlers called io.ReadAll on the request body without any size cap, so a single large POST from a run's runner token can consume all available memory and terminate the Gitea process, denying service to all users. The issue is rated CVSS 6.5 (availability-only, PR:L - authenticated, no user interaction), affects Gitea 1.22.0 through 28.1.0, and is fixed in 28.2.0; no public exploit code was identified and EPSS is only 0.16% (4th percentile), consistent with an SSVC assessment of no observed exploitation and low automatability.
Denial of service in the ip-address npm library before 10.7.4 allows unauthenticated remote attackers to consume CPU and stall applications that pass untrusted input containing many '%' characters into the Address6 IPv6 constructor. The flaw is CWE-1333 inefficient regular expression / quadratic complexity, rated medium severity (CVSS 4.0 base 6.3), with availability-only partial impact; exploitation depends on a reachable application code path that forwards attacker-controlled data to Address6 parsing (CVSS AT:P). No public exploit code was identified at time of analysis, and upgrading to 10.7.4 or later removes the condition.
Gitea before 28.2.0 allows a user with write access to a repository's releases to link an existing issue or comment attachment into a release by supplying its UUID, because the release attachment-linking routine validated the repository and release association but not whether the attachment was already bound to an issue or comment. This exposes the attachment's file name, size and download count and lets the attacker rename or delete it. The flaw is limited to the same repository and requires knowledge of a non-enumerable UUID, and no public exploit or active exploitation has been identified at time of analysis (EPSS ~0.15%).
Resource exhaustion denial of service in AUTOMATIC1111 stable-diffusion-webui up to and including 1.10.1, where a crafted .safetensors model file with a manipulated metadata header-length field causes excessive allocation when the model is loaded. Remote attackers can only trigger this by convincing a user to download and load the malicious model file (mandatory user interaction), so an idle service cannot be attacked directly. Publicly available exploit code exists (a POC zip is referenced), but impact is confined to availability of the web UI process - no data disclosure or code execution - and the project has not released a fix despite being notified via issue report.
Cross-site scripting in AUTOMATIC1111 stable-diffusion-webui (through version 1.10.1) is triggered when the Extra-Networks Card Builder renders the __metadata__.sshs_model_hash field from a safetensors model without output encoding, letting a crafted value execute script in the victim's browser session. Exploitation is unauthenticated from the network perspective but requires the victim to load or import an attacker-supplied model file, so delivery depends on social engineering or a poisoned model repository, and impact is confined to the user's browser rather than leading to server-side code execution. Publicly available exploit code exists (no CISA KEV confirmation), and the project has not responded to the upstream issue, so no patched release is currently identified.
Cross-site scripting in AUTOMATIC1111 stable-diffusion-webui through 1.10.1 lets an attacker inject script into the Extra Networks 'Card Builder' view by crafting a malicious filename for a model, LoRA, embedding, or hypernetwork card that create_item_html in modules/ui_extra_networks.py renders without proper escaping. Attackers must first place a file with that crafted name into a scanned networks directory; a user then triggers execution simply by opening the affected view, so no credentials are needed (CVSS 4.0 base 5.3, PR:N/UI:P). Publicly available exploit code exists (E:P) and the vendor has not responded to the issue report, but impact is limited to low-integrity script execution in the victim's browser, and the default localhost bind means remote exploitation requires a deliberately network-exposed instance (--listen or --share).
Code injection in AUTOMATIC1111 Stable Diffusion WebUI through 1.10.1 lets remote attackers execute attacker-chosen Python objects when a victim loads a malicious third-party model whose YAML configuration supplies a crafted 'target' value to get_obj_from_str in modules/sd_models.py. User interaction is mandatory - the victim must import the untrusted model/config - but no authentication is needed on the attacker side because the payload travels inside distributed model files; publicly available exploit code exists and a proof-of-concept ZIP is referenced. No CISA KEV entry confirms active exploitation, and the vendor has not responded to the early issue report, so no vendor-released patch was identified at time of analysis; the supplied CVSS 4.0 score of 2.1 conflicts with the independently assessed CVSS 3.1 vector, which rates post-load confidentiality, integrity, and availability impact as high.
SQL injection in the Exam Module of itsmeravitejak Online Examination System allows an authenticated low-privilege user to manipulate the topicid argument in exam.php's Exam::startExam function and alter database queries, with the independent assessment indicating high confidentiality impact, low integrity impact, and no availability impact. The issue affects the unversioned rolling-release codebase through commit e6208e630b14657999bbfe4c9912302d2a1e2449, and publicly available exploit code exists; there is no CISA KEV confirmation of active exploitation. Despite the public exploit, real-world priority is low because a valid application login is required and no vendor-fixed release is available.
Reflected cross-site scripting (CWE-79) in the Search argument of /abs.php in hrisikeshpal Blood Bank Management System 1.0.0 lets a remote, unauthenticated attacker inject script that executes in a victim's browser session. Exploitation requires the victim to load an attacker-crafted request (UI:P passive user interaction), so it depends on link-delivery or social engineering against a running instance rather than direct compromise; confidentiality and availability impact is assessed as none, with only limited integrity impact inside the victim's session. Publicly available exploit code exists and the flaw was disclosed through a GitHub issue that the project has not yet answered; no vendor-released patch was identified at time of analysis, and EPSS/KEV data was not provided.
Java deserialization in DataStax pulsar-jms through 9.0.3 allows a low-privileged publisher to trigger unsafe object decoding in consuming JMS clients via crafted ObjectMessage content, potentially causing limited confidentiality, integrity, and availability impact, or code execution when a suitable gadget chain is present. Publicly available exploit code exists, but exploitation requires the consumer to process ObjectMessage payloads and depends on classpath gadgets for meaningful code-execution impact. No vendor-released fixed version is identified, and the project has not responded to the reported issue.
Default-password exposure in Diem CMS through 5.1.3 allows remote attackers to access unhardened installations whose credential, provisioned through dmCorePlugin/lib/data/dmDataLoad.php, was never rotated. Publicly available exploit code exists and the vendor has not responded to the project issue; the practical risk is limited to deployments with the default configuration left in place, making this a low-to-moderate priority issue despite network reachability.
Out-of-bounds heap reads, and under a non-default configuration out-of-bounds heap writes, in librtmp as shipped with RTMPDump through 2.6 let an unauthenticated attacker who controls or intercepts an RTMP server corrupt or leak memory inside the connecting client. AMF3_Decode ignores failures returned by the AMF3 property decoder, so an oversized AMF3 string length supplied by the server is trusted and used against buffers it does not actually describe, producing an over-read of heap bytes; the write primitive is only reached when the client is invoked with the --token option that enables the DecodeTEA path. Scored 6.1, with no public exploit identified at time of analysis, and real exposure confined to hosts that actively act as RTMP clients against attacker-reachable servers.
Authorization bypass in ProjectSend 2.0.0 through 2.6.x lets authenticated staff holding the import_orphans permission delete or adopt files owned by other users by submitting non-canonical path aliases such as './a/b.txt' to the orphan import or delete endpoints. The root cause is an incorrect-order validation flaw in OrphanFileScanner::isOrphan() (CWE-180): path strings are compared before Flysystem normalization, so a spelling that storage rewrites to a real tracked path is misclassified as an orphan and the delete_others_files boundary is bypassed. The issue is fixed in ProjectSend 2.7.0; exploitation requires a staff account granted import_orphans and the presence of other users' files, and no public exploit was identified at time of analysis.
Stack-based buffer overflow in libstrophe through 0.14.0 allows a malicious or compromised XMPP server to crash or corrupt the stack of a connecting client during SCRAM SASL authentication: a server-first-message whose base64 s= (salt) attribute decodes to more than 124 bytes overruns the fixed 128-byte stack buffer in SCRAM_Hi(). Only clients that perform SCRAM authentication and connect out to an attacker-controlled or compromised server are exposed, so the flaw is client-side and requires the victim to initiate the connection rather than exposing an attack surface at scale. Impact is predominantly denial of service (process abort), with limited stack memory overwrite possible only in NDEBUG builds where the guarding assertion is compiled out; no public exploit code or confirmed active exploitation (CISA KEV) is identified at time of analysis, though a technical write-up of the flaw is publicly available.
Missing authorization in the Scheduled Restore component of David-Crty Databasement 1.8.1 and earlier lets an authenticated user supply an arbitrary schema_name value to the SaveScheduledRestoreRequest API endpoint and thereby schedule restore operations against database schemas they are not authorized to manage. Exploitation is network-reachable but requires a valid privileged session on the instance plus the Scheduled Restore feature being in use, and public exploit code exists per the vendor GitHub security advisory. The issue is fixed in release 1.8.2; impact per the assessed vector is limited to low confidentiality, integrity and availability effects on the appliance's own scope.
Stack-based out-of-bounds write in lwIP's mDNS response handler affects lwIP through 2.2.1 when the optional mDNS application is compiled in and the device is performing an mDNS service search. An unauthenticated attacker on the same local link can send a multicast PTR answer with an oversized RDLENGTH or an SRV answer with RDLENGTH below 6, corrupting a 256-byte stack buffer and causing a crash with possible limited integrity impact. Patch guidance is available via an upstream commit, no public exploit identified at time of analysis, and no CISA KEV entry is present; the assessed severity is moderate (CVSS 6.0).
Cleartext password storage in Soarkey StudentManagement through commit e08f7f1d5015af407aa4cca0ada3dea189b4937e allows local low-privileged users to recover sensitive credentials handled by the UserDao.login flow in code/src/service/AdminDao.java. The issue is CWE-312 and is local-only with a CVSS score of 1.9; publicly available exploit code exists, but the project is an unmaintained student codebase with negligible production deployment, so real-world risk is very low.
Account takeover in Gitea 0 through 28.1.0 via the OpenID association callback, which accepts a positive OpenID 2.0 assertion without verifying that the signed-in victim initiated the linking. A remote unauthenticated attacker who controls an OpenID provider can trick a signed-in user into opening a crafted link, link the attacker's identity to the victim's account, and then sign in as the victim through OpenID login, bypassing local TOTP/WebAuthn checks. Exploitation requires OpenID login/association to be enabled and user interaction; no public exploit code has been identified, EPSS is 0.11% (1st percentile), and the vendor has released Gitea 28.2.0 to fix it.
Heap out-of-bounds read in librtmp (RTMPDump) through 2.6 can crash RTMP clients when AMFProp_Decode parses an AMF0 strict-array element count without first confirming that four bytes remain. The issue is unauthenticated from the network perspective but requires the victim to initiate an RTMP session with an attacker-controlled server or for an attacker to be positioned as a man-in-the-middle; impact is limited to availability (client crash), with no code execution or confidentiality impact established. No public exploit code was identified at time of analysis.
Cross-site request forgery in Dyad's OAuth Callback Handler affects Dyad through version 1.16.0 and can let a crafted dyad:// callback be accepted without proof that it belongs to a legitimate in-app connection flow, causing an integrity-only credential/integration state change. Exploitation is remote but requires the Dyad desktop app to be installed with its custom-protocol handler registered and requires the victim to launch or approve the crafted protocol link; there is no confidentiality or availability impact per the independent assessment, and the CVSS 4.0 base score is 5.3. Vendor-released patch: 1.17.0-beta.1; no public exploit identified at time of analysis.
Unauthenticated requests to Gitea's organization home route can trigger a nil-pointer panic and HTTP 500 when the path segment resolves to an individual user instead of an organization. The issue affects Gitea through 28.1.0 and is fixed in 28.2.0; it requires no authentication or special configuration, but each request causes only per-request availability degradation (error response and logged panic), not a full service crash. EPSS is 0.19% (8th percentile) and no public exploit has been identified at time of analysis.
Incorrect authorization in OneUptime 14.0.2 through 14.0.68 allows an authenticated project member holding the AI-access admin-set permission to act on Kubernetes clusters that their label- and owner-based scope does not cover, including probing agent RBAC permissions via the AI access test, resetting/disconnecting agents, approving pending kubectl changes, and steering incident AI conversations into running commands on unauthorized resources. The flaw is reachable only where cluster management and AI agent features are actually in use, and the incident-conversation path is limited to read-only kubectl/infrastructure commands; no public exploit code was identified at time of analysis and the issue is not in CISA KEV. Vendor-released patch: 14.0.69, with a documented regression test suite exercising per-cluster edit scope through the real user middleware.
Stored cross-site scripting in the Bootstrap Shortcodes plugin for WordPress before 3.4.6 allows authenticated users with Contributor-level access or higher to inject arbitrary web script through a crafted id attribute in the [bs_tcontent] shortcode, which is rendered into an unquoted HTML attribute; a victim must view the page and interact with the injected element for the script to execute. The issue is rated CVSS 5.1 and there is no public exploit identified at time of analysis; the vendor has released version 3.4.6 with a fix that quotes the attribute.
Weak SHA1-based password hashing in the Diem PHP framework's PluginDmUser handler (lib/model/doctrine/PluginDmUser.class.php, versions through 5.1.3) lets anyone who already holds the stored password hashes from a Diem user database recover plaintext credentials offline far faster than a modern key-derivation function would allow. Exploitation is strictly local and high-complexity and presupposes a prior foothold to obtain the hashes, so the weakness yields no remote or unauthenticated path into the application; impact is limited to confidentiality of credentials and any password reuse elsewhere. Publicly available exploit code exists (referenced upstream issue 452), the project was notified but has not responded, and no CISA KEV listing or EPSS score was supplied with the intelligence.
Signed-in Gitea users can bypass the interaction restriction of a locked issue by adding or removing emoji reactions on the issue and its comments through the web UI, even though they lack write access and the REST API correctly refuses the same operation. The gap affects Gitea through 28.1.0 and is limited to reaction toggling - no issue text, comment content, labels, or repository state can be altered - so the practical consequence is cosmetic noise and notification churn on issues maintainers deliberately froze. There is no public exploit identified at time of analysis, CISA SSVC records no known exploitation, and EPSS is 0.18% (7th percentile), consistent with a low-severity authorization inconsistency rather than a high-impact access-control failure; the vendor-released fix is Gitea 28.2.0.
Information disclosure in Gitea 1.22.0 through 28.1.0 allows an authenticated low-privileged user who can create a draft release to obtain attachment metadata from repositories they cannot read, as well as metadata for abandoned uploads. The draft-release API path builds an assets list from an unsaved release whose ID is 0, causing the attachment lookup to return file name, UUID, upload time, size, and download count, but not attachment contents. CISA SSVC reports exploitation: none, no public exploit was identified at time of analysis, and EPSS is 0.16% (4th percentile).
Gitea leaks private repository metadata to users whose access has since been revoked: the GET /api/v1/user/subscriptions and /api/v1/user/starred endpoints returned name, description, clone URLs, owner and counters for every watched or starred private repo without re-checking current permissions, so a user who starred a private repo while authorized and later lost access (for example via a team permission downgrade or collaborator removal) could keep reading that metadata with an otherwise valid account. The flaw is fixed in 1.27.0 and 28.0.0 and was disclosed with 28.2.0; EPSS is only 0.15% (4th percentile), there is no KEV listing and no public exploit code identified at time of analysis, and the CVSS 4.3 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) reflects that an attacker must already be authenticated and must previously have held legitimate access, with only metadata - not repository contents - exposed.
Incorrect authorization in Gitea's label-deletion logic lets an authenticated user with write access to a repository's issues delete issue labels belonging to an unrelated organization whose numeric ID happens to match that repository's ID. Exploitation requires the coincidental ID collision between a repository and an organization, cannot be chosen by the attacker, and yields only limited integrity impact (deleted labels) with no confidentiality or availability loss; Gitea instances through 28.1.0 are affected and 28.2.0 fixes the flaw. Risk is low: EPSS is 0.15% (4th percentile), SSVC marks exploitation as none and non-automatable, and no public exploit code was identified at time of analysis.
Established BGP peers can bypass IPv6 FlowSpec validation in CZ.NIC BIRD when the receiving flow6 channel has unicast-route validation enabled, because BIRD reconstructs a prefix with zero-filled skipped bits instead of rejecting a destination component with a nonzero offset as RFC 8956 section 5 requires. This allows the peer to inject a FlowSpec rule matching a broader set of IPv6 destinations than its advertised unicast route authorizes, potentially causing downstream traffic filtering or redirection where export policy permits propagation and downstream devices enforce the rule. Exploitation is limited to authenticated peers with a suitable unicast route and the validation-enabled flow6 configuration; no public exploit was identified at time of analysis, and an upstream fix is available via commit 7cf75587b6f38b87849fe192bf5dfd124b7702bc.
Authenticated users of Teable can rename folders that belong to bases they have no membership in by submitting a folderId from a foreign base to the PATCH /api/base/:baseId/node/folder/:folderId endpoint, which validates the base|update permission only against the baseId in the URL rather than against the base that actually owns the folder. The flaw is an IDOR / authorization bypass (CWE-639) affecting releases prior to release.2026-10-12T12-45-53Z.3331; the vendor-supplied CVSS 4.0 vector scores it 2.3 and our independent CVSS 3.1 assessment scores it AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, reflecting integrity-only impact with no data disclosure or destruction. Exploitation requires a valid Teable session plus discovery of a non-enumerable foreign folderId, so multi-tenant or shared deployments carry the most practical exposure; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV).
Gitify desktop builds prior to 7.10.0 perform the GitHub web OAuth flow without generating or validating an OAuth `state` value, so an attacker who supplies their own authorization code via a crafted `gitify://oauth?code=...` deep link can bind a victim's Gitify client to the attacker's GitHub account. The attacker then controls the notifications the victim sees, but gains no access to the victim's data and no account takeover - impact is limited to low integrity. Exploitation is unauthenticated (PR:N) but requires a race against an already-pending login (AT:P) and victim interaction with the attacker's link (UI:P). No public exploit code or CISA KEV entry was identified at time of analysis, and the issue is assessed as genuinely low priority.
Code injection in WongKinYiu YOLOv9 0.1 via the ONNX metadata handler allows an attacker who supplies a tampered .onnx model to execute code when DetectMultiBackend parses the model's 'names' and 'stride' fields; exploitation is unauthenticated but requires the victim to load the untrusted model (UI:P), making the realistic threat a supply-chain or malicious-pretrained-model scenario rather than direct compromise of a passive service. Publicly available exploit code exists, and the project has not responded to the issue report; signals are mixed and point to a low operational priority despite a serious weakness class.
Reflected cross-site scripting (CWE-79) in the abandoned open-source PHP application Books4Cash allows unauthenticated remote attackers to inject arbitrary script into the search page by crafting a malicious 'Search' argument accepted by search.php. The payload is returned to the browser without sanitization, so the impact is confined to the victim's session - an attacker can execute script in the context of the site, deface or alter content, and potentially capture session data or perform actions as the victim. Exploitation is not unattended: a victim must follow an attacker-supplied link (CVSS UI:P social-engineering prerequisite), and publicly available exploit code exists per the CVSS 4.0 E:P metric and VulDB disclosure. Real-world exposure is limited because the project repository has been dormant for years and has a negligible deployment footprint; no CISA KEV entry indicates active exploitation.
Stored cross-site scripting in Chamilo LMS's Ticket Module lets authenticated users who can create or edit ticket projects inject a script payload through the project Name field, which executes when another user views the affected page. The flaw affects Chamilo LMS up to 1.11.40, 2.0.3, and 3.0.1 and requires victim interaction; publicly available exploit code has been disclosed, though no CISA KEV active-exploitation confirmation is present. The vendor fix is visible in PR #9228 and commit cb6fe2127e587603451c609b4ed78c0293fcc3fa, and builds applying that output-encoding patch are not exploitable.
Terminal escape sequence injection in alexpasmantier television through 0.15.9 allows a local attacker who controls an entry's output, such as a crafted filename, to write unsanitized control characters to the victim's terminal after the TUI exits, provided the victim selects that entry. The CVE is tracked as CWE-77 command injection and rated CVSS 4.8, but PR #1125 adds sanitize_for_display for control characters, indicating the practical issue is terminal escape/control-character injection rather than direct command execution. The CVSS vector notes E:P (Proof-of-Concept exploit maturity), but no CISA KEV active exploitation is confirmed; exploitation requires local staging and victim interaction, making this a low-priority issue.
In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix NULL current_pwq deref in flush dependency check check_flush_dependency() uses current_wq_worker() to determine whether the caller is a workqueue worker and then dereferences worker->current_pwq to test whether the current workqueue is WQ_MEM_RECLAIM. current_wq_worker() only means that %current has PF_WQ_WORKER set. A kworker can reach check_flush_dependency() while it is not executing a work item. One such path is worker_thread() acting as the pool manager, where create_worker() does GFP_KERNEL allocation and the allocation path invokes the OOM notifier. In that state worker->current_pwq is NULL because current_pwq is set only by process_one_work() and cleared again after the work function returns. [ 416.760634][ T375] Call trace: [ 416.760638][ T375] check_flush_dependency+0x80/0x120 (P) [ 416.760648][ T375] __flush_work+0x98/0x224 [ 416.760657][ T375] flush_work+0x30/0x44 [ 416.760665][ T375] ... [ 416.760710][ T375] blocking_notifier_call_chain+0x58/0xa0 [ 416.760719][ T375] out_of_memory+0xb4/0x458 [ 416.760730][ T375] __alloc_pages_may_oom+0x11c/0x1a8 [ 416.760739][ T375] __alloc_pages_slowpath+0x314/0x46c [ 416.760746][ T375] __alloc_frozen_pages_noprof+0x110/0x1a4 [ 416.760753][ T375] new_slab+0x12c/0x484 [ 416.760759][ T375] ___slab_alloc+0x7a8/0xc7c [ 416.760765][ T375] __slab_alloc+0x74/0xd8 [ 416.760772][ T375] __kmalloc_cache_node_noprof+0x2ac/0x304 [ 416.760779][ T375] alloc_worker+0x28/0x60 [ 416.760785][ T375] create_worker+0x4c/0x20c [ 416.760790][ T375] worker_thread+0xe8/0x2b8 [ 416.760796][ T375] kthread+0x1a8/0x200 [ 416.760805][ T375] ret_from_fork+0x10/0x20 Guard the WQ_MEM_RECLAIM-worker warning with worker->current_pwq. If the kworker is not currently executing a work item, there is no current workqueue to diagnose with that warning. The PF_MEMALLOC warning is left unchanged so explicit reclaim context flushing a !WQ_MEM_RECLAIM target is still reported.