Stale account-confirmation links in blueprintUE self-hosted edition 4.3.3 and earlier never expire, so anyone who later obtains an old confirmation email - from a compromised mailbox, an archived backup, forwarded mail, or server logs - can still activate an account that was never meant to be confirmed. The impact is confined to unauthorised account activation plus evasion of the optional unconfirmed-user purge job; the token does not expose the password and does not by itself constitute account takeover. The vendor's GHSA-qp6g-7v4v-33r9 advisory documents a proof-of-concept procedure, no CISA KEV entry exists, and the issue is scored medium (supplied CVSS 4.0 base 6.3; assessor CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N), which places it on a 'this month' remediation cadence rather than an emergency one.
Cookie attribute injection in the Effect TypeScript framework's makeCookie() lets an application that feeds untrusted strings into the cookie name, domain, or path fields serialize extra attributes into Set-Cookie headers. Affected releases are @effect/platform from 0.1.0 up to but excluding 0.97.1, and effect from 4.0.0-beta.0 up to but excluding 4.0.0-beta.103; a crafted domain such as "legit.com; Domain=.parent.tld" widens the cookie to a parent domain because RFC 6265 takes the last Domain occurrence, and SameSite=None or Max-Age can be appended but only when the caller has not set those options itself. No public exploit was identified at time of analysis, and vendor fixes ship in @effect/platform 0.97.1 and effect 4.0.0-beta.103.
Sessions remain valid in AshAuthentication after a victim resets or changes their password, so an attacker who already holds one of the victim's session tokens stays signed in despite the credential change. Only deployments using the log_out_everywhere add-on with apply_on_password_change? true (which mix ash_authentication.install writes by default) - combined with tokens enabled, store_all_tokens? true and require_token_presence_for_authentication? true - are affected, and only when the password is changed through a non-atomic action such as the generated password reset action or the installer's change_password action; versions 4.5.0 before 4.15.1 and 5.0.0-rc.0 before 5.0.0-rc.16 are impacted. Severity is medium (CNA score 6.3 under CVSS 4.0; assessor vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N), no public exploit has been identified at time of analysis, and vendor-released patches are available in 4.15.1 and 5.0.0-rc.16.
Parsing untrusted BSON binary vector data in 32-bit builds of the MongoDB C Driver's BSON library can trigger an arithmetic element-count wraparound, causing the operation to report success after processing only a fraction of the attacker-supplied elements. The result is a silent data-integrity divergence from byte-oriented accessors and from 64-bit builds, which are unaffected; there is no memory corruption or information disclosure. No authentication or user interaction is required beyond inducing the application to parse the data, and no public exploit was identified at time of analysis.
GNU Gatekeeper (gnugk) before 5.16 can be crashed by a deliberately short application-defined RTCP probe packet delivered to the H.460.24 media port, because H46024Socket::ReceivedProbePacket() copies 20 bytes from offset 12 of the frame without first checking that the frame is long enough, producing a heap over-read. Only gatekeepers that have H.460.24 NAT traversal in use and have an H.460.24 probing exchange in progress are reachable by the flaw, so realistic impact is limited to process termination on a network-reachable, unauthenticated but timing-constrained path rather than data disclosure or code execution. No public exploit has been identified at time of analysis, and version 5.16 contains the vendor fix.
An out-of-bounds heap read in GNU Gatekeeper (gnugk) before 5.16 lets a remote RTP peer crash the gatekeeper by sending a crafted RTCP SDES packet on the media proxy port of an in-progress proxied H.323 call. The vulnerable ParseRTCP() code in ProxyChannel.cxx treats the SDES item payload as a NUL-terminated string, so an item that lacks a terminating NUL causes a length-based read past the received packet when EnableRTCPStats is enabled - a non-default option - and the only demonstrated impact is denial of service (A:H, no confidentiality or integrity impact). The vendor addressed it in release 5.16 via commit e8939d0, and no public exploit code or in-the-wild activity was identified at the time of analysis; severity is medium (vendor CVSS 4.0 base 6.3) because exploitation requires a live, media-proxied call plus RTCP statistics processing.
AshAuthentication 5.0.0-rc.4 through rc.15 can be brute-forced without limit against password sign-in, password-reset requests, magic-link requests and one-time-password flows, because a configured brute_force_strategy only attaches its preparation to the actions the strategy generates itself and never verifies that resource-defined actions carry it. Projects scaffolded with mix ash_authentication.install followed by mix ash_authentication.upgrade, or with mix ash_authentication.add_strategy.otp, end up in precisely that unprotected state, and OTP sign-in under registration_enabled? true escapes protection entirely because preparations do not run on create actions. The unauthenticated attack is a guessing campaign, not a single-shot exploit, so the practical outcome is account takeover by password or OTP guessing plus unlimited password-reset and magic-link email generation; the vendor-released fix is 5.0.0-rc.16 and no public exploit code or active exploitation has been identified at time of analysis.
Authenticated users of Label Studio can turn the export converter into a full-read SSRF primitive: importing a task whose data.image points at an internal service and then requesting an export in YOLO_WITH_IMAGES, YOLO_OBB_WITH_IMAGES or COCO_WITH_IMAGES makes the server issue an HTTP GET to the attacker-chosen URL and write the response bytes into the ZIP the same user downloads, giving back the body rather than a blind probe. The same request can additionally leak the organization owner's long-lived API token to an attacker-controlled host when the Host header is spoofed so its netloc matches the task URL (ALLOWED_HOSTS defaults to '*'), though on a stock instance that token is inert while legacy_api_tokens_enabled stays off. Affected are Label Studio before 1.23.2 and label-studio-sdk before 2.1.2; the GitHub advisory contains a step-by-step proof-of-concept reproduction, and the issue is not listed in CISA KEV, so this is a genuine but mid-tier, this-month priority rather than an emergency.
Predictable email-ownership verification tokens in Cotonti through 1.0.0 let unauthenticated remote attackers activate accounts or confirm email addresses they do not control. Because tokens are generated as md5(microtime()), an attacker who reads the server's HTTP Date header can pin the whole-second portion of the timestamp, brute-force the sub-second component offline (roughly one million candidates per targeted second), and replay any matching 32-character token to the users.register.php validate handler. Severity is rated CVSS 4.0 6.3 with AC:H reflecting the microsecond-guessing requirement that limits reliability and scale; no public exploit identified at time of analysis, and priority is this_month per vulnerability intelligence scoring.
Unauthenticated SCIM directory read in Padloc through 4.3.0 lets remote attackers retrieve provisioned user and group records - usernames, emails, names, externalIds and group memberships - from the SCIM endpoints of any organization that has directory provisioning configured, simply by supplying any non-empty bearer token. The attacker must know the target organization id, which is embedded in the SCIM request URL path, and the flaw is read-only: it exposes directory metadata but does not permit modification of directory data and is inert where SCIM provisioning is not enabled. Severity is moderate (CVSS 4.0 base 6.3; assessed CVSS 3.1 6.3, confidentiality-only) with priority 'this_month'; no public exploit code or active exploitation has been identified at time of analysis.
Request smuggling in Wasmtime's wasi-http component allows a malicious WebAssembly guest to make the host forward HTTP requests carrying multiple conflicting content-length headers, potentially causing a downstream server or intermediary that does not reject such messages to interpret request boundaries incorrectly and enabling limited integrity impact. Affected releases are before 36.0.19, 37.0.0 before 48.0.7, and 49.0.0 before 49.0.4; fixed versions are 36.0.19, 48.0.7, and 49.0.4. This is a moderate, conditionally exploitable issue rather than a top-priority emergency, and no public exploit was identified at time of analysis.
Wasmtime's wasi-http p3 (WASIp3) implementation does not pass forwarded body trailers through the embedder's WasiHttpHooks::is_forbidden_header check, so a WASIp3 guest that forwards an existing request or response body can attach trailers that escape embedder-customized forbidden-header restrictions. Versions 46.0.0 through 48.0.6 and 49.0.0 through 49.0.3 of the rust/wasmtime-wasi-http crate are affected; the issue is network-reachable and unauthenticated per the CVSS v4.0 vector (6.3), but impact is limited to integrity of trailer filtering with no confidentiality or availability effect, and it only matters to embedders that customized the hook beyond DEFAULT_FORBIDDEN_HEADERS. There is no CISA KEV entry and no public exploit identified at time of analysis, and the vendor advisory states there is no known attack this enables even though it can undermine a property the embedder intended to enforce.
Parse Server deployments backed by MongoDB can have stored field values corrupted by a write that uses a dot notation key with a null value beneath a field that is not an object or array, such as a Pointer, Number, String, Date or Boolean field, or an internal field like createdAt or the ACL. The flaw is an input-validation gap (CWE-20): the same key with a non-null value was already rejected, but the null case bypassed field type validation and MongoDB then wrote a sub-document beneath the scalar field, which can make reads return a sub-document instead of the expected value, render an object entirely unreadable when an internal date field is hit, or break later atomic operations on a number field. The CVSS 4.0 score is 6.3 and the independently assessed CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L: an unauthenticated remote caller can trigger it where class-level permissions or ACLs permit public writes, otherwise the attacker must already hold write access to the affected object, and PostgreSQL deployments are not affected because they reject such writes. No public exploit code and no confirmed active exploitation were identified at time of analysis (not in CISA KEV), and vendor patches are released in 8.6.111 and 9.10.6-alpha.3.
Reflected cross-site scripting (CWE-79) in the authentication endpoint of WSO2 API Manager, WSO2 Identity Server and WSO2 API Control Plane lets an unauthenticated remote attacker inject JavaScript that executes in a victim's browser when the victim follows an attacker-crafted request or link (CVSS 3.1 base 6.1, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). Successful exploitation requires user interaction and social engineering, and the vendor states that session-related sensitive cookies carry the httpOnly flag, so session hijacking and cookie theft are not achievable; realistic outcomes are browser redirection to attacker-controlled sites, modification of page content shown to the user, and exfiltration of non-httpOnly browser-accessible data. No public exploit code has been identified at time of analysis, and the issue is not listed as actively exploited; priority is 'this_month' rather than immediate.
DOM-based cross-site scripting in the billboard.js charting library before 4.1.3 lets attacker-influenced series ids or names execute JavaScript in the browser of anyone viewing a chart built with a custom HTML legend. Only applications that set both legend.contents.bindto and legend.contents.template, use a template that leaves a tag open after the {=TITLE} placeholder, and feed untrusted or third-party data into series identifiers are exposed; default legends and trusted-only series data are not. CVSS 6.1 reflects the requirement for user interaction and the non-default configuration, EPSS is low at 0.16% (5th percentile), there is no CISA KEV entry, and the upstream advisory published by Naver includes a public PoC reference that has not been independently verified as working exploit code. The issue is a bypass of the sanitize step that was added for CVE-2026-1513 and is fixed in 4.1.3.
ArcReel 0.32.0, 0.33.0 and 0.34.0 contain a server-side request forgery flaw in the Provider Test-Connection endpoint at /api/v1/providers/{id}/test. An attacker who holds an authenticated session with enough privilege to invoke that test-connection feature can manipulate the destination so the ArcReel server issues a request on their behalf, potentially reaching internal services and exposing low-sensitivity information. A public proof-of-concept reference exists but is not verified as working exploit code, no CISA KEV entry is recorded, and the vendor did not respond to early contact; the assessed impact is limited to low confidentiality with no integrity or availability effect.
Umami 3.3.x, 3.4.0, and 3.4.1 can allow a user who already holds valid first-factor credentials to complete login without the second factor when an administrator has configured an enforced 2FA policy. The result is a bypass of mandatory two-factor authentication in the login handler at src/app/api/auth/login/route.ts, rated 5.3 (moderate) in the supplied assessment. A public PoC reference exists; it is not verified as working exploit code, and the issue is limited to deployments where enforced 2FA is enabled.
Session fixation in the CloudClassroom-PHP-Project login handler (loginlinkadmin.php) allows a remote, unauthenticated attacker to influence the PHPSESSID value and then have a victim complete authentication under that session identifier, taking over the resulting authenticated session. The code path around session_regenerate_id does not prevent the attacker-supplied identifier from persisting, so impact is limited to Low confidentiality and integrity with no scope change. A public PoC reference exists; it is not verified as working exploit code, and there is no CISA KEV entry or other confirmation of active exploitation. The product is unversioned, the vendor did not respond to the disclosure, and no vendor-released patch was identified at time of analysis.
Path traversal in the zt-zip Java library's Zips fluent unpack API lets a malicious archive entry such as '../escape/poc.txt' (or a trailing-slash directory entry like '../escape/') be written outside the configured destination directory, affecting versions 1.17 and earlier and covering both the normal copy branch and the ZipEntryTransformer branch. Only applications that extract untrusted archives through Zips.get(zip).unpack().destination(dir).process() are exposed; code that uses ZipUtil.unpack(...) is unaffected because that path already performs a destination-boundary check. Rated 6.1 Medium (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L) with integrity impact only and no direct network trigger, it requires the victim application to process an attacker-supplied archive; a public PoC reference exists in the upstream advisory, and no active exploitation has been confirmed.
Path traversal in phpMyAdmin's MoTranslator library through version 6.0.1 lets an attacker who can influence the 'locale' argument reaching Loader::getTranslator in src/Loader.php cause translation files to be resolved from outside the intended directory, exposing local files (low confidentiality impact, per the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). The CVSS vector requires low-privileged authenticated access (PR:L), and real-world reachability depends on the consuming application wiring remote request data into the 'locale' parameter, since MoTranslator is a library rather than a standalone network service. No CISA KEV entry exists, but a public PoC reference has been disclosed (not verified as working exploit code), the vendor was contacted and did not respond, and no fixed version is listed in the available data.
An infinite loop in the ShapeRecord::loadFromFile parser of phpMyAdmin ShapeFile (versions up to and including 4.0.1) allows remote attackers to stall or hang the importing process by supplying a crafted ESRI .shp file, consuming CPU until the process is killed or times out. No authentication is required, but the crafted shapefile must actually be fed into the SHP import/parse path for the condition to fire, so exposure is limited to deployments that accept externally supplied shapefiles. Impact is confined to availability (VA:L) with no confidentiality or integrity effect; a public PoC reference exists, but it is not verified as working exploit code, and there is no confirmed active exploitation (no CISA KEV listing).
Stored cross-site scripting in Tactical RMM 1.6.2 and earlier lets a user with a console session persist HTML/JavaScript into automated-task, schedule and dropdown option labels, which then execute in the browser of any other user - typically an administrator - who opens a page rendering those labels, exposing the victim's session and console privileges. The root cause is CWE-79: the tacticalrmm-web front end passed these stored values to Vue's v-html directive, which deliberately bypasses the framework's HTML escaping. NVD rates it 6.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), while our assessment raises the privilege requirement to PR:L because writing the poisoned fields requires an authenticated session; the issue is not in CISA KEV, active exploitation is not confirmed, but public proof-of-concept material is referenced (SSVC Exploitation: poc, with a GitHub repository targeting v1.5.2), and vuln.today priority is this_month.
Cross-workspace information disclosure in ZaneOps 1.14.0 through 1.15.1 allows an administrator of any single workspace to read another tenant's pending fork preview environment - including plaintext environment variables cloned from the target project's base environment and the preview basic-auth credentials - by calling the ReviewPreviewEnvDeployAPIView GET endpoint with a victim project slug and environment name. Both parameters are published by ZaneOps itself in a public comment on the fork pull request, so nothing has to be guessed, but the route is read-only and exposure is confined to previews still in the PENDING (unapproved) state on multi-workspace deployments. Exploitation requires an authenticated workspace administrator (PR:L, a self-created workspace suffices); a public PoC reference exists but is not verified as working exploit code, and no active exploitation has been confirmed.
Out-of-bounds write in the MongoDB Atlas SQL ODBC Driver affects applications that fetch a value of a particular database type into a fixed-width client-side target: the driver renders the value into a textual form longer than the target the ODBC interface defines and copies it without limiting the copy to the buffer's real size. Exploitation requires an authenticated database user with basic write privileges who can store such a value, plus a consuming application that retrieves it into a fixed-width bound target, so the realistic outcome is memory corruption that terminates the client application rather than code execution or data disclosure (CVSS 4.0 base 6.0; independently assessed as CVSS 3.1 AV:N/AC:H/PR:L/UI:N/C:N/I:L/A:H). No public exploit was identified at time of analysis, the issue is not in CISA KEV, and the priority decision is this_month - a moderate-severity, moderate-priority issue rather than a top-tier emergency.
Uninitialized-memory disclosure in the MongoDB C Driver's legacy GridFS file handling allows an authenticated database user with ordinary write access to a shared GridFS storage area to set up conditions under which a separate application later appends to the affected file, causing bytes left over in the application's process memory - potentially including credentials - to be written into records that same user is permitted to read. Because the trigger depends on that second application's append behavior and on the legacy code path being in use, the leak is opportunistic rather than guaranteed and the issue is a moderate, authenticated information-disclosure risk rather than an urgent widespread threat. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor tracks the defect as CDRIVER-6508.
Path traversal in the datadir plugin of ruTorrent before 5.3.20 lets an authenticated user escape the configured topDirectory jail and have the web server create directories and move torrent data to locations outside it. The root cause is that correctDirectory() compares the submitted datadir as written and does not resolve symbolic links, while the downstream mkdir/rename/copy operations do follow them; an attacker who can place a symlink under their own top directory and then submit a datadir path through it can redirect torrent data to any path writable by the web server or rtorrent, such as the web root. Exploitation requires a valid ruTorrent account with datadir plugin access and the ability to create that symlink; no public exploit code was identified at time of analysis, and the vendor fix is in 5.3.20.
Client-side use-after-free in FreeRDP's urbdrc USB redirection channel lets a malicious RDP server crash a connecting client that runs with /usb enabled while a matching local USB device is being announced. FindChannelById returns a raw channel pointer without taking a reference, and the control-channel CLOSE_REQUEST path frees that channel without holding the device manager's loading_lock, so the libusb announcement thread can read channel->Write from freed memory. Triggering requires the victim to initiate the connection with USB redirection active and to win a narrow timing window (AC:H/AT:P); a PoC harness shipped with the vendor advisory demonstrates the use-after-free under AddressSanitizer, but it is not an end-to-end RDP reproduction and is not verified as working exploit code, and no active exploitation has been reported.
Improper certificate validation in HPE Networking Fabric Composer lets a remote attacker who already occupies an on-path (man-in-the-middle) position present a fraudulent TLS certificate that the product accepts, enabling interception of transferred files and stored credentials for remote servers. No authentication or user interaction is required, but HPE states success depends on preconditions outside the attacker's control, which is why the score is capped at CVSS 5.9 (AC:H) despite high confidentiality impact. No public exploit code or active exploitation is identified in the available intelligence, and the reported priority is this_month rather than an emergency.
Insufficient session expiration in the API of HPE Networking Fabric Composer can allow an authenticated administrative attacker to keep a session alive and retain persistent access when preconditions outside the attacker's control are met. The vulnerability is rated CVSS 5.9 with PR:H and AC:H, making it a moderate-severity persistence issue rather than an initial-access path; no public exploit has been identified at time of analysis. The HPE advisory is the authoritative source for affected versions and remediation.
Improper certificate validation in HPE Fabric Composer lets an authenticated low-privilege attacker obtain sensitive information, with high confidentiality impact and limited integrity impact (CVSS 5.9). Network access is required and high attack complexity means additional conditions must hold, but the available sources do not describe the specific trigger. No public exploit code or confirmed active exploitation is identified at time of analysis.
Information disclosure in MongoDB Database Tools versions 3.1.4 through before 100.20.1 allows an authenticated user who can modify GridFS file metadata to set the stored filename to '-' and cause a later authorized mongofiles get_id retrieval without --local to write the file contents to standard output instead of a local file. The attacker only gains access to content they cannot read directly if a higher-privileged operator performs that retrieval and the captured standard output is readable by the attacker, making exploitation highly conditional; no public exploit was identified at time of analysis.
Denial of service in the Eclipse Vert.x Redis client (io.vertx:vertx-redis-client) 4.0.0 through 4.5.35 and 5.0.0 through 5.2.2 lets a malicious, compromised or man-in-the-middle Redis server exhaust the client's heap and crash the JVM. Two triggers are documented: a server that streams bytes on an EOL-terminated line (such as a simple string) without ever sending the terminating CRLF, which grows the read buffer without bounds because no configurable line limit exists, and a crafted RESP bulk string with a missing or corrupt CRLF trailer (for example `$3\r\nfooXX`) that drives the parser into an infinite loop, re-parsing the same buffer and re-emitting the same response to the consumer until memory is exhausted. The flaw is remotely reachable without authentication (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, 5.9) and affects only availability - confidentiality and integrity are not impacted - with the significant precondition that the client must be talking to an attacker-controlled or compromised endpoint; a public proof-of-concept reference exists, but it is not verified as working exploit code, and there is no CISA KEV confirmation of active exploitation. Fixed versions are 4.5.36 on the 4.x branch and 5.2.3 on the 5.x branch.
µD3TN daemon crashes and denial of service can result from a use-after-free in the Bundle Protocol version 6 (BPv6) fragmenter cleanup path. The flaw is reachable by remote, unauthenticated attackers per the CVSS vector, but triggering it requires the node to be processing BPv6 bundles and a memory allocation to fail during cleanup, so reliable exploitation depends on memory pressure or resource constraints. No public exploit code has been identified at the time of analysis and active exploitation has not been confirmed; the CVSS 5.9 score reflects availability-only impact with high attack complexity.
Denial of service in µD3TN allows an unauthenticated, remote sender of BPv6 (Bundle Protocol version 6) traffic to crash the bundle node by driving the fragmenter's block-duplication code path into a double free, but only if a heap memory allocation fails at that exact point (CVSS 5.9, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, availability-only). Because that allocation-failure precondition is not attacker-controlled, practical exploitation generally requires first inducing memory pressure or exhaustion on the target node, which is why the vector carries AC:H. No public exploit code and no CISA KEV entry were identified at time of analysis, and the vuln.today priority is this-month remediation rather than emergency response.
WP Fastest Cache, a WordPress caching plugin, writes the full response of Core's wp-activate.php to a publicly readable cache file in versions up to and including 1.5.3, ignoring that endpoint's no-store/no-cache headers, its wp-activate-* cookie, and the WP_INSTALLING state. Because WordPress prints the new account's plaintext username and twelve-character password on that activation screen, unauthenticated attackers who can request the cached file can read the credentials of the most recently activated Multisite registrant. The exposure is heavily gated: the site must be a Multisite subdirectory installation with both public user and site registration enabled, and a real registrant must have just followed their activation link; the vulnerability is not known to be actively exploited (no CISA KEV entry) and no public exploit code was identified at time of analysis.
Improper certificate validation in the HPE Networking Fabric Composer API allows an unauthenticated attacker positioned on the same adjacent network as a client to have a forged or substituted certificate accepted, exposing sensitive information read through that API channel. Impact is confidentiality-only (CVSS 5.7, C:H/I:N/A:N) and exploitation is not silent: the vector requires a legitimate client interaction (UI:R) plus an adjacent network position (AV:A) and a man-in-the-middle vantage point inside the management network. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the current priority is a this-month patching cadence rather than emergency response.
Docker Buildx versions v0.19.0 through v0.38.0 can skip the fs.read entitlement approval when a single Bake invocation builds multiple targets, allowing an untrusted Bake definition to read files that are accessible to the Buildx client without the expected approval prompt. The victim must actively run the attacker-controlled Bake definition, and the lapse occurs only under unspecified 'certain conditions' and only in multi-target builds; single-target builds are not affected per the advisory. Impact is limited to confidentiality of files already reachable by the Buildx client, and Docker fixed the issue in v0.38.1; no public exploit code or active exploitation is identified in the available data.
Unauthorized analytics record injection affects Umami through 3.4.1 because the Record API endpoint accepts a Website identifier without verifying that the caller controls that site. Remote unauthenticated attackers who know or guess a website ID can write to or pollute another site's analytics data, with limited integrity and availability impact and no confidentiality exposure; this is a medium-severity authorization issue, not a drop-everything emergency. A public disclosure includes exploit details, but working exploit code is not independently verified and active exploitation is not confirmed in the provided KEV data.
A divide-by-zero in NVIDIA nvJPEG (CWE-369) lets an attacker crash applications that decode a crafted JPEG image through the library, producing a denial of service with no code execution or data exposure. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R, A:H) requires the malformed image to reach a locally running nvJPEG consumer and a user or application to actively process it, so exposure is limited to environments that feed untrusted images into nvJPEG-based decoding such as image services and ML preprocessing pipelines. No CISA KEV entry, no confirmed public exploit, and no patch version are present in the supplied intelligence; the NVIDIA product-security advisory for 2026 (5910) is the root reference, and this is a moderate-severity availability issue rather than a top-priority emergency.
Sensitive information disclosure in HPE Fabric Composer's web-based management interface allows an unauthenticated remote attacker to obtain sensitive information when a legitimate interface user performs an action, making user interaction the primary limiting factor. The issue is rated CVSS 5.4, and the independent assessment bounds impact to low confidentiality with no integrity or availability effect; the specific triggering request or feature is not described in the available sources. No public exploit identified at time of analysis, and KEV status is not indicated in the supplied intelligence.
Opening and traversing a crafted HDF5 file can crash the application because H5HL_unprotect() in HDF5 through 2.2.0 may pass a NULL local-heap pointer to H5AC_unpin_entry(). The bug is a CWE-476 NULL pointer dereference: if the metadata cache destroys a corrupted local heap entry and H5HL__prfx_dest() clears heap->prfx or heap->dblk, the final unprotect has nothing to unpin, causing an assertion failure in debug builds and a crash in release builds. Impact is limited to local denial of service with user interaction and no confidentiality or integrity loss; the supplied CVSS 4.0 vector has E:P (proof-of-concept maturity), but no CISA KEV listing or confirmed working exploit code was provided.
Open redirect in the TYPO3 'mail' extension's click tracking middleware allows an unauthenticated remote attacker to craft a tracking link on a trusted TYPO3 site that forwards victims to an arbitrary external destination, turning the site's own domain into a phishing lure. It is rated CVSS 5.3 (medium) by the vendor and CVSS 4.0 5.3 by the reporting source, with the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N - the practical impact is limited to integrity of the redirected-to context, so risk is social engineering rather than direct compromise. No public exploit code or PoC is referenced in the available intelligence and the issue is not in CISA KEV; the vendor priority label places it in the this-month remediation window.
Saving the backend module configuration of the third-party TYPO3 extension "mail" writes the submitted settings into page TSconfig without restricting them to the module's own configuration keys, allowing arbitrary page TSconfig injection. The flaw affects installations running the extension (CPE cpe:2.3:a:typo3:extension_"mail" with no version bound) and is reachable by a backend user who holds a valid account and has been granted access to the mail module - no victim interaction is required and attack complexity is low, but permissions are required, so it is not unauthenticated. Impact is integrity-only and low (assessed CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N); no public exploit code has been identified at time of analysis, no EPSS score or CISA KEV entry was supplied, and the vuln.today priority decision is this_month rather than an emergency.
The TYPO3 extension "mail" (EXT:mail) performs server-side fetches of content referenced by an "external URL" mail - the message body, its stylesheets and its embedded images - without validating the destination host, allowing server-side request forgery against internal network services. Exploitation requires a valid TYPO3 backend account that holds access to the mail module, so the attacker is an authenticated operator/insider rather than an anonymous outsider; no user interaction is needed and the behaviour is the extension's default. Impact is limited to low-confidentiality disclosure of what internal hosts return, with no integrity or availability effect, and an independent assessment rates the issue moderate with a this-month priority; no public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV.
HTTP 500 responses generated by RESTEasy's default exception mapper embed the unhandled exception's localized message, so a remote unauthenticated client that can induce such an exception receives whatever text that message carries (CWE-209). The behavior was reproduced on RESTEasy 7.0.2.Final and, per the CPE data, flows into a wide set of Red Hat products that bundle RESTEasy, including Red Hat Build of Quarkus and Keycloak, JBoss EAP 8 and its expansion pack, Fuse 7, Satellite 6, Red Hat Build of Apache Camel 4 for Quarkus 3, Red Hat Build of Apicurio Registry 3 and Red Hat Build of Debezium 3; complete affected and fixed version ranges remain unconfirmed. No public exploit was identified at time of analysis, and the confidentiality impact is capped by the actual content of the leaked message rather than by arbitrary memory or file exposure. Priority is 'this_month' rather than immediate.
Error messages returned by the Exchange RPC in Octo STS 0.11.1 and earlier disclose the contents of trust policies to callers whose OIDC token does not satisfy them. Remote, unauthenticated callers who hold any validly signed OIDC token from an accepted issuer (for example a GitHub Actions token from a repository they own) and who know or guess a target owner/repo plus identity name can read the policy's issuer, subject and audience patterns, claim_pattern regexes, and app pin details - information that frequently names internal repositories, branches, environments or cloud account identifiers, even when the policy lives in a private repository. The flaw is confidentiality-only: no token minting or trust-policy bypass is possible; the vendor issued a fix in v0.11.2 (commit 88c6432), and no public exploit was identified at time of analysis.
Axxon One deployments before version 3.2.0 on Windows and Linux expose their full user and role inventory to any authenticated low-privilege account: the security configuration API's user configuration request returns the complete lists of users and roles regardless of the caller's permissions. Because the flaw only requires valid credentials for an ordinary account and no user interaction, it lowers the barrier to privilege mapping and follow-on targeting, though it grants no modification or disruption capability. There is no public exploit code or confirmed active exploitation, and the available signals rate this as a low-urgency, non-emergency information disclosure to be scheduled for this month's patch cycle; upgrading to 3.2.0 removes the exposure.
Incorrect authorization in the Health Monitoring service of AxxonSoft AxxonNet on Linux (versions before 3.28.0) lets a remote attacker who already holds a shared report token - a credential intended only for read-only report access - create, modify, or delete monitoring alerts through the monitoring API. The flaw is a scope-enforcement failure rather than an authentication bypass in the strict sense: a valid low-privilege token is a hard prerequisite (PR:L, AV:N), and the resulting impact is limited to alert integrity and availability, with no confidentiality loss and no path to code execution. Severity is medium (CVSS 4.0 base 5.3; independently assessed CVSS 3.1 5.3, S:U/C:N/I:L/A:L); there is no CISA KEV listing and no public exploit identified at time of analysis, so the practical risk is suppression or forgery of health alerts by someone who already has report-level access.
GitHub Enterprise Server releases prior to 3.23 expose a limited out-of-bounds read in the Git service daemon (babeld) that lets an SSH-connected user recover a small amount of adjacent process memory. The flaw sits in the SSH host-key possession-proof code, where babeld sized the session identifier using the current digest length instead of its own; an attacker who already holds an account with SSH access can re-key to a signature algorithm with a longer hash and cause neighboring memory to be signed and returned to the client. The prerequisite of an authenticated account with SSH access and the 'limited amount' of recoverable data bound this to a medium-severity confidentiality leak (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) with no integrity or availability impact, and no public exploit has been identified at time of analysis.
Cross-site request forgery in GitHub Enterprise Server (all versions prior to 3.23) allows an unauthenticated attacker to delete stored Slack and Microsoft Teams ChatOps configuration and provider credentials by luring a signed-in Management Console operator's browser into issuing a tokenless cross-site GET to the integration removal endpoint. Exploitation is not opportunistic: the instance must already have ChatOps integrations configured and the operator must visit attacker-controlled content while authenticated to the Management Console, with the disruption to notifications and commands materializing only when configuration is applied or services are reloaded. Severity is medium (vendor CVSS 4.0 base 5.3; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:R with low integrity and availability impact and no confidentiality exposure), no public exploit code has been identified at time of analysis, and fixes are available in 3.19.14, 3.20.10, 3.21.8 and 3.22.3.