Missing authorization controls in the Brocade Fabric OS REST API on releases before 10.0.1 allow any authenticated API user - regardless of assigned role or administrative scope - to retrieve complete Monitoring and Alerting Policy Suite (MAPS) violation data across all logical switches. The exposure is limited to information disclosure of chassis-wide health metrics, port performance violations, and configuration data; there is no write, code-execution, or availability impact, and the attacker must already hold valid Fabric OS credentials and have adjacent/management-network reachability to the API. There is no public exploit identified at time of analysis, and the issue is best characterized as a modest-priority information disclosure flaw rather than a system-compromise vector.
IBM Guardium Data Protection 12.0, 12.1 and 12.2 ship the WfpMonitor kernel driver, whose METHOD_NEITHER IOCTL handlers dereference caller-supplied pointers without consistent probing or exception handling, so a local attacker who already holds high privileges on the host can trigger a system crash or obtain limited reads of kernel memory. The CVSS 3.1 vector (AV:L/PR:H/UI:N, C:L/I:N/A:H, score 5.1) confirms the flaw is local-only and requires pre-existing elevated privileges, meaning it grants no privilege escalation and has no integrity or code-execution impact. There is no CISA KEV entry and no public exploit code identified at time of analysis, and a vendor patch is available, making this a moderate-to-low real-world priority that is best handled through routine driver patching.
Hard-coded credentials embedded in the Ticket Ryutsu Center Android application (wavedash_co.,_ltd.) let anyone who downloads the publicly available Google Play package recover an API key used by the app through static analysis or decompilation. The vector (AV:L/PR:N/UI:N) shows the only prerequisite is local access to the distributed binary, meaning the extraction requires neither authentication nor user interaction, though the real-world blast radius depends entirely on the backend scope and permissions conferred by that key, which the JVN advisory does not document. Impact is therefore scored as limited confidentiality disclosure (CVSS 4.0, C:L/I:N/A:N per the independent assessment, which matches the NVD vector for this unauthenticated local-access flaw); no public exploit code and no confirmed active exploitation were identified at time of analysis.
MongoDB C Driver can store or use incorrect numeric values when parsing over-precision Decimal128 strings that contain leading zeros and should have been rejected. The issue affects applications built on the driver that parse attacker-controlled decimal strings, including via Extended JSON, and is limited to data integrity (C:N/I:L/A:N) with no public exploit identified at time of analysis; exploitation requires the embedding application to accept external decimal input. This is a low-to-moderate priority issue rather than a high-urgency flaw.
Data corruption in luksmeta allows a local attacker who already holds administrative privileges to damage or destroy metadata and encrypted payload data stored on a Linux Unified Key Setup (LUKS) device when a new metadata entry is saved. Because faulty free-space boundary calculations and flawed overlap detection can let new records be written past the available area or on top of existing ones, integrity is fully compromised though confidentiality is not (CVSS 5.1, AV:L/AC:L/PR:H/UI:N/C:N/I:H/A:L), and affected volumes may become inaccessible. Exploitation requires local host access with privileges sufficient to run luksmeta and write to the device; there is no remote or unauthenticated vector, no public exploit identified at time of analysis, and no confirmed active exploitation (not in CISA KEV), so impact is realistically limited to accidental or deliberate corruption by a privileged operator. The issue affects luksmeta as shipped with Red Hat Enterprise Linux 7, 8, 9 and 10, plus Red Hat OpenShift Container Platform 4 through the underlying RHCOS userland.
Server-side request forgery in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) lets an authenticated user who satisfies high-complexity preconditions make the appliance send requests to destinations of the attacker's choosing, enabling internal network enumeration and reconnaissance that can support follow-on attacks. Rated CVSS 4.9 (AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N), this is a moderate-severity, low-priority issue rather than an emergency: exploitation requires a valid authenticated session plus the ability to reach a request-handling function that accepts an attacker-influenced destination, and there is no public exploit identified at time of analysis, with real-world impact bounded by whatever sensitive internal hosts the gateway itself can reach. IBM has published an advisory covering these builds, and other versions are not in scope.
Keycloak, including the Red Hat Build of Keycloak and Red Hat Single Sign-On 7, exposes the active primary secret of confidential clients to any authenticated realm administrator who holds only the read-only view-clients role. The flaw sits in the installation provider and client registration endpoints, which return client credentials that a read-only administrator should never be able to read; with the leaked secret an attacker can authenticate as the confidential client and inherit its service account permissions across integrated services. Exploitation requires an existing realm administrator account with the view-clients role, so risk scales with how broadly that low-trust role is delegated, and no public exploit has been identified at time of analysis.
Improper certificate validation in GnuTLS 3.8.13 causes applications that rely on it for TLS trust decisions to accept certificates carrying invalid extensions, letting an attacker who can intercept a connection impersonate a trusted server and read or modify the protected traffic. The assessed vector requires a man-in-the-middle position rather than remote-at-will access, but once that position exists no credentials or user interaction are needed, and the NVD score of 9.1 reflects high confidentiality and integrity impact. Publicly available exploit code exists (a GitHub PoC repository and an associated gist), CISA's SSVC evaluation marks the issue as PoC-exploited, automatable, with total technical impact, and no CISA KEV entry has been recorded at time of analysis.
Uninitialized memory disclosure in FFmpeg's HDR10+ dynamic metadata serializer (av_dynamic_hdr_plus_to_t35()) lets crafted Matroska T.35 BlockAdditional or HEVC/AV1 SEI metadata cause up to three bytes of stale process memory to be written into remuxed or transcoded output files. All FFmpeg versions through 9.0.2 are affected; CVSS 4.0 scores this 4.8 (AV:L/UI:P/C:L) and the independent assessment concurs at CVSS 3.1 4.8 with only confidentiality impact, because the leak is bounded to a few bytes, requires the victim to actively process the file, and gives the attacker no control over the leaked contents. There is no public exploit identified at time of analysis and no CISA KEV listing, but an upstream fix commit and pull request are already available, making this an internally consistent low-to-moderate priority remediation item rather than an urgent one.
Predictable per-booking access hashes in the Booking Calendar WordPress plugin before 11.8 let unauthenticated attackers read a booking's personal data or modify the booking in place, provided they can determine or closely estimate when that booking was created. The flaw is rated CVSS 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N), reflecting that no login or victim interaction is needed but that the attack is targeted and per-booking rather than mass-exploitable, since the low-entropy, time-seeded value behind each hash must be narrowed down first. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); vendor remediation is available in version 11.8.
An out-of-bounds read in the bundled IJG JPEG decoders of OFFIS DCMTK 3.7.0 (libijg8, libijg12 and libijg16) lets a crafted DICOM file whose JPEG stream carries a Huffman table with a difference category above 15 drive the decoder past the end of the small static extend_test[] and extend_offset[] lookup tables, producing incorrectly decoded pixel data or a crash and disclosing a bounded amount of adjacent process memory. Exploitation is unauthenticated (CVSS PR:N) but strictly local in vector: the attacker must deliver the file and the victim must decompress it (UI:P), and the same exposure applies to dcmdjpeg and any application that decompresses JPEG DICOM images with DCMTK. Default builds are affected because the DCMTK_ENABLE_STRICT_HUFFMAN_TABLE_CHECK guard is disabled by default; no public exploit identified at time of analysis, SSVC records Exploitation: none and Automatable: no, and the vendor fix is available as a source commit.
A heap-based out-of-bounds read in OFFIS DCMTK 3.7.0's DcmRLECodecDecoder::decodeFrame() allows unauthenticated local attackers to read up to 63 bytes of adjacent heap memory or cause a crash by tricking a victim application into decoding a crafted RLE Lossless DICOM file whose pixel data fragment is shorter than the 64-byte RLE header. Exploitation requires user interaction to open or process the malicious file and only affects applications using the frame-by-frame decoding path (e.g., via DcmPixelData::getUncompressedFrame()); the dcmdrle command-line tool is not affected. The issue is fixed in commit 45469f3c30037e9c7159290e4bb74cd7b3b9ef1d, and no public exploit code has been identified at time of analysis.
Improper handling of custom URL schemes in the Android application Ticket Ryutsu Center allows a malicious co-resident app on the same device to send a crafted Intent that causes the victim app to open an arbitrary website. Exploitation requires a separate attacker-controlled application to already be installed and depends on user interaction; impact is limited to low integrity violation with no code execution, data theft, or availability loss. No public exploit identified at time of analysis, and the issue is assessed as genuinely low priority.
Cross-organization repository metadata disclosure in the Katello (Red Hat Satellite 6) Docker Tags repositories API allows an authenticated user who holds product-view permissions in one organization to retrieve repository configuration data for Docker meta tags owned by a different organization by simply supplying that foreign tag identifier. The weakness is an authorization-scoping gap (CWE-639, IDOR-style) correctly rated CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), with impact limited to low-severity confidentiality loss - there is no write or denial-of-service effect. Exploitation requires valid credentials, multi-organization deployment, and knowledge or enumeration of valid foreign tag identifiers; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS data was not supplied.
Missing authorization in Event Tickets 5.30.0.1 and earlier allows an authenticated low-privileged WordPress user, such as a subscriber or customer, to perform a restricted event-ticket action they should not be authorized to perform. The affected product is the Liquid Web/StellarWP Event Tickets WordPress plugin, and the issue carries a moderate CVSS score of 4.3 with only low integrity impact and no confidentiality or availability impact. Exploitation requires a valid login but no victim interaction, and no public exploit identified at time of analysis.
Authenticated information disclosure in the Easy Digital Downloads WordPress plugin before 3.7.1 allows any subscriber-level account to read other customers' recent order contents and harvest signed download links that grant free access to paid digital files. The flaw rates CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, CWE-200) because exploitation requires a valid low-privilege login, making it most dangerous on sites that allow open or self-service registration. No public exploit identified at time of analysis; vendor-released patch: 3.7.1.
Information disclosure in the Wallet System for WooCommerce plugin before 2.8.0 allows any authenticated user on a WordPress site - the description states a subscriber-level account is sufficient - to generate and download a report containing every customer's wallet transaction history, including names, email addresses, user roles, transaction amounts, payment methods and dates. The report endpoint performs no capability check and instead trusts a token that the plugin renders on a front-end page, so any logged-in user can retrieve the token and then invoke the endpoint; no user interaction is required. The published base score is 4.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, while our assessment rates the confidentiality impact as High (C:H) because the exposure covers complete customer PII and the store's full financial transaction ledger. No public exploit code identified at time of analysis; patch available in 2.8.0.
Deletion of stored form entries in the WordPress plugin Database Addon for WPForms (also distributed as 'wpforms entries') is possible against any site running a version before 1.1.1, because the entry-removal handler fails to validate a CSRF nonce when that field is omitted and performs no capability check of its own. An attacker can host a crafted page that, when loaded by a logged-in WordPress administrator, silently submits the deletion request on the victim's behalf; the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N confirms network reachability and low complexity but gates success on administrator interaction. Impact is integrity-only (C:N/I:L/A:N, CVSS 4.3 Medium) and limited to removal of stored form submissions, with no code execution, data disclosure, or site availability loss; there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).
Missing per-session authorization in Indico's legacy session export API (all versions prior to 3.3.13) allows any authenticated user who can access a parent event to pull metadata - session title, description, and conveners - for restricted sessions they are not permitted to view. Exploitation requires a valid Indico account plus legitimate access to the containing event, and the leaked data is read-only, so impact is limited to low-severity information disclosure (CVSS 4.3, PR:L, C:L only). There is no public exploit identified at time of analysis, and the flaw is corrected in 3.3.13 via a vendor-released patch.
Session exhaustion in Progressive Robot hMailServer 6.2.28 through 6.3.5 lets any user who holds valid credentials for a single mailbox repeatedly log in and keep the server's shared browser-session table full, causing the least-recently-used eviction logic to terminate other users' webmail and administration sessions, including those of the server administrator and support staff. Because the table is global rather than per-account and imposes no cap on how many concurrent sessions one account may hold, the attacker does not need elevated privileges or special access - only network reachability to the REST API endpoint (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, assessed as an authenticated-remote availability issue). Impact is limited to denial of service against idle sessions, with no code execution, data disclosure, or integrity impact, and no public exploit identified at time of analysis; upgrading to hMailServer 6.3.6 clears the condition.
Offline tokens issued by Keycloak, Red Hat Build of Keycloak, and Red Hat Single Sign-On 7 can stay valid after a backchannel logout because a serialization bug in the OIDC Dynamic Client Registration (DCR) response omits the backchannel-logout offline-token-revocation setting, silently disabling it whenever a client is updated through the standard update flow (CVE-2026-107623, CVSS 3.1 4.3, CWE-862). The actor must hold client-management/registration privileges (AV:N/PR:L), and the deployment must use DCR and rely on backchannel logout to revoke offline tokens, so this is a loss of a revocation guarantee rather than an account takeover. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; EPSS signal is not available in the supplied data, and the assessed real-world risk remains low.
Missing authorization checks in the VillaTheme Core WordPress plugin, affecting versions up to and including 1.0.5, allow an authenticated low-privilege user to reach plugin functionality that should require higher capabilities, resulting in limited information disclosure. The flaw carries a CVSS 3.1 score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) and per the assessed vector is not exploitable by unauthenticated users - an account on the WordPress site is a prerequisite (PR:L). No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; impact is limited to low confidentiality exposure with no integrity or availability effect, making this a moderate, low-priority issue.
Expired JSON Web Tokens can keep being accepted by fast-jwt through version 6.3.3 when the verifier is created with caching enabled (cache: true) and a token carries an exp claim but no iat claim. In src/verifier.js, cacheSet only derives an exp-based cache deadline when iat is present, so the entry falls back to the generic cacheTTL (600000 ms / 10 minutes by default), and a later cache hit returns the stored payload before expiration is revalidated - allowing an attacker who already holds such a token to replay it past its expiry for up to the cache TTL. The attacker cannot forge or alter a token, and the CVSS vector indicates a low-privilege authenticated context (PR:L); no public exploit code and no confirmed active exploitation were identified at time of analysis. The issue is fixed in 6.3.4.
Authentication bypass in CISA's Malcolm network traffic analysis platform lets any host with network adjacency to the Malcolm deployment reach the bundled Arkime live-capture service directly on TCP port 8005 and impersonate arbitrary users, gaining full administrative access to the Arkime viewer. The issue stems from documented default configuration: the arkime-live container runs with network_mode: host and binds the viewer to 0.0.0.0 (viewHost), Arkime trusts the X-Forwarded-User header from any source IP (userAuthIps=::,0.0.0.0/0) with automatic user creation, and the passwordSecret is the hardcoded public value 'Malcolm'. Exploitation is unauthenticated and requires no user interaction, but it does require adjacency to a network segment the Malcolm host is attached to, because the attacker must connect to port 8005 directly and bypass the nginx front end; deployments that block 8005, restrict userAuthIps, or change the passwordSecret are not exploitable by this path. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); CISA's ICS assessment publishes a base score of 4.2, while our independent assessment rates confidentiality impact as High (unauthenticated reads of captured traffic and viewer data) for a materially higher score.
Out-of-bounds memory access in the phalFelica module of NXP NXPNfcRdLib on RC663-based NFC reader deployments (versions through 07.14.00_Pub) can corrupt or expose memory when an API caller supplies values that the library fails to bounds-check, resulting in limited loss of confidentiality, integrity, and availability. Exploitation requires local access with high privileges and high attack complexity per the assessed CVSS vector (AV:L/AC:H/PR:H), so there is no remote or unauthenticated path, and no public exploit has been identified at time of analysis. The issue is rated low severity (CVSS 3.9) and is remediated in NXPNfcRdLib 07.18.00 and later, making patching straightforward for teams able to update the library.
A domain-denylist bypass in Pydantic AI's local web-fetch tooling (web_fetch_tool and the WebFetch local fallback) lets an attacker-influenced model reach a host the operator explicitly placed in blocked_domains by supplying a DNS-equivalent spelling - an IDNA/fullwidth form, a non-ASCII label separator, a case variation, or a trailing root label - that does not string-match the configured entry but resolves to the same host. Affected are pydantic-ai and pydantic-ai-slim versions 1.77.0 through 1.107.5 and 2.0.0b1 through 2.44.0; the flaw is a denylist bypass only, so configurations that use allowed_domains fail closed and are unaffected, and the private-IP and cloud-metadata SSRF protections remain effective, meaning internal or metadata endpoints are not reachable through this bug. Rated CVSS 3.1 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) as a low-severity, high-complexity information-fetch issue, with no public exploit identified at time of analysis and vendor patches available in 1.107.6 and 2.44.0.
Silent in-place corruption of caller-supplied buffers occurs in the npm package msgpack5 before version 6.1.0 whenever the decoder parses a negative signed 64-bit integer (MessagePack int64, 0xd3): the two's-complement negation is written back into the very bytes of the caller's input buffer. The bug is network-reachable but high-complexity to exploit and low-impact - CVSS 3.1 base score 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N, unauthenticated per the PR:N vector) - because it yields no code execution, no memory disclosure and no denial of service; the only consequence is that an application which retains or reuses the same buffer after decoding (for integrity/hash checks, logging, or later re-processing) may see silently altered values. Only negative int64 values are affected; positive integers and all other MessagePack types are untouched, applications that discard or copy the input before decoding are unaffected, and there is no public exploit or CISA KEV record - confirmed active exploitation has not been reported and no POC was identified at time of analysis. Version 6.1.0 contains the vendor fix.
GnuTLS 3.8.13 incompletely enforces X.509 name constraints during certificate-chain validation, allowing an attacker who already controls a constrained subordinate Certificate Authority to issue certificates for domains outside its permitted namespace and thereby bypass cross-domain PKI restrictions. The victim must be a relying party using the affected version to validate such a chain; the forged certificate is then accepted without user interaction, yielding limited confidentiality and integrity impact. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS is very low (0.12%, 2nd percentile), while our independent assessment rates the issue more severely than the vendor-published CVSS 3.7 because successful abuse of a trusted-CA position fully defeats the name-constraint control.
Certificate validation bypass in GnuTLS 3.8.13 allows an attacker who can introduce a crafted end-entity X.509 certificate into the verification path to obtain sensitive information, because the library fails to reject certificates carrying a contradictory combination of Key Usage (KU) and Extended Key Usage (EKU) values. The flaw is remotely reachable without authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:N), and CISA's SSVC assessment rates it automatable with partial technical impact; no public exploit has been identified at time of analysis and the issue is not in CISA KEV. Exploitation is meaningful only where a consuming application actually relies on KU/EKU constraints for its trust decisions, and it requires a man-in-the-middle position on the TLS path or control of a server or endpoint the victim connects to.
Stored cross-site scripting in Eimzamip versions v1.6.4 up to but not including v1.6.7 allows an authenticated user to persist script-related HTML into a field that is later rendered to other users without neutralization. Exploitation requires a valid low-privileged account (PR:L per the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N vector) plus a second user who views the poisoned page (UI:R), so unauthenticated or fully automated mass attacks are not possible. At CVSS 3.5 this is a low-severity issue; no public exploit has been identified at time of analysis, and CISA's SSVC decision data records Exploitation: none and Automatable: no.
The Magic: The Gathering Arena Windows/Steam client (builds 2026.59.30.12801.127931.6 and certain later 2026.60.x builds) hands a server-supplied home-screen carousel GoToExternalUrl value straight to the Windows shell via Application.OpenURL/ShellExecuteW without validating the URI scheme or domain, so any URI-scheme handler registered on the host - including ones a client would never expect, such as ms-calculator: - can be invoked with no user interaction. Exploitation requires the attacker to already control the carousel content delivered to clients, either by compromising the game's content backend or by intercepting the content channel on an adjacent network; that precondition is the primary limiter and is why this is assessed as a low-priority issue despite the unusual primitive (CVSS 3.1 base 3.4; NVD AV:A versus an assessed AV:N with AC:H, PR:N, UI:N, S:C, and only low integrity impact). There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, though a public technical writeup of the flaw exists; the practical impact is further bounded by which dangerous scheme handlers happen to be registered on a victim machine and whether one of them can be chained into a separately exploitable action.
Authenticated agents can bypass per-record authorization in the Appointment Booking Plugin (LatePoint) before 5.6.9, enabling them to read and modify other agents' profile data and read other agents' bookings and customer details when the optional AI Abilities API feature is enabled. The flaw is a CWE-639 authorization bypass via user-controlled keys. No public exploit code or active exploitation has been identified, and the assessed CVSS is low (3.3) due to the requirement for an authenticated agent account and the optional feature.
Booking Calendar, a WordPress plugin, fails to restrict which WordPress options a lower-privileged user can retrieve through one of its settings handlers, so an authenticated account holding the Editor role or higher can read the values of arbitrary entries in the site's options table - including core site configuration - in plugin versions from 10.15 up to but not including 11.8.3. The issue is rated CVSS 3.1 2.7 (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N), reflecting a network-reachable but high-privilege-only path with limited confidentiality impact and no integrity or availability effect. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the practical risk is concentrated on sites that hand Editor-level access to untrusted or compromised accounts. A vendor-released patch exists: 11.8.3.
Authenticated WordPress users holding contributor-level access or higher can clone, modify, reorder, and write plugin metadata onto galleries and images owned by other users on any site running the Image Photo Gallery Final Tiles Grid plugin before 3.6.14. The root cause is incomplete object-ownership verification in the plugin's gallery and image management actions, where authorization is checked against a different object than the one being acted on or omitted entirely, producing a low-integrity authorization bypass with no confidentiality or availability impact. No public exploit code or active exploitation has been identified at time of analysis, and real-world risk is low because an attacker must already possess a contributor account on the target site; a vendor-released patch is available in version 3.6.14.
Cross-site user data disclosure in the SMS Alert WordPress plugin before 4.0.1 allows an administrator of one subsite on a WordPress multisite network to retrieve stored billing phone numbers belonging to users of other subsites on that network. The flaw only affects multisite installations, and exploitation further requires the SMS Alert SMS gateway credentials to be configured and stored on the acting administrator's own site; the attacker must already hold administrator privileges on at least one subsite (CVSS vector PR:H, authenticated), so this is realistically a cross-tenant disclosure by a trusted or compromised admin rather than unauthenticated remote exploitation. Scoring is low (vendor score 2.7; our assessment is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N), no public exploit code has been identified at time of analysis, and there is no indication of active exploitation (not in CISA KEV); patched plugin version 4.0.1 is available from the vendor.
Irreversible deletion of orders, customers, and transactions stored by the Appointment Booking Plugin for WordPress is possible for authenticated backend staff users in all versions before 5.6.5, because the plugin's deletion routine never confirms that the acting staff account is authorized for the specific record it is asked to remove. An attacker holding a record-scoped staff role (for example, a staff member whose scope is limited to their own appointments) can supply an arbitrary record identifier and destroy data belonging to other staff or entirely outside their assigned scope, and the deletion cannot be undone. The vulnerability is network-reachable and requires no user interaction, but the principal barrier is the prerequisite of an existing backend staff login, which keeps the practical risk low and consistent with the vendor's 2.7 score; no public exploit code has been identified at time of analysis.
Heap out-of-bounds write in Mutt's convert_file_from_to() charset conversion routine can be triggered when a user adopts an attacker-supplied email message as a composition template, letting a crafted Content-Type header drive the conversion past the end of an allocated buffer. Exploitation is local and user-driven: the victim must deliberately invoke the template workflow on the malicious message (CVSS 3.1 AV:L/AC:H/PR:N/UI:R, base score 2.5; the internal assessment results in the same base metric group with a Low rather than None availability impact), and favorable memory conditions are needed for the out-of-bounds write to occur reliably. Mutt versions up to and including 2.4.2 are affected per EUVD, no public exploit has been identified at time of analysis, and no vendor-released patch version is confirmed in the available data.
Information disclosure in Pydantic AI's OpenTelemetry instrumentation (vulnerable ranges >= 0.3.4, < 1.107.6 and >= 2.0.0b1, < 2.44.0) lets sensitive agent content reach telemetry backends even when the content-redaction setting InstrumentationSettings(include_content=False) is enabled, because exception events, exception stack traces, error status descriptions, and the serialized model_request_parameters attribute were never covered by that setting. Affected deployments must have OpenTelemetry instrumentation active, must have configured include_content=False, and must actually hit an error path - a tool ModelRetry/ToolFailed, a tool-code exception, a validation error, or a failed model request, embedding, or image-generation call - for the leak to occur; data reaches only parties who already have read access to the configured telemetry backend, so no new access to agent data is granted. There is no public exploit identified at time of analysis, no CISA KEV listing, and the assessed severity is low (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N), with vendor-released patches available in 1.107.6 and 2.44.0.
Pydantic AI's OpenTelemetry instrumentation fails to redact validation-retry prompt content from exported telemetry, so agents configured with InstrumentationSettings(include_content=False) can still leak model-generated invalid values into span attributes such as gen_ai.input.messages and pydantic_ai.all_messages. Only deployments using structured output modes that skip tool calls (NativeOutput or PromptedOutput) or output validators on text output are exposed on this specific code path; tool-call retries and installations that never set include_content=False are unaffected. Disclosure is limited to parties able to read the telemetry backend, and no public exploit code or confirmed active exploitation has been reported; assessed CVSS is low (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N, CVSS 4.0 base 2.3).
Incorrect type conversion in the BeamMCP (beam_mcp) Elixir library from 0.1.0 before 0.10.1 causes an authenticated MCP client's JSON boolean and null tool arguments to arrive at the host's dispatch function as the Elixir strings "true", "false" and "nil"; because a string is truthy in Elixir, a host that branches on truthiness - for example `if args.dry_run` or a `confirm: false` guard - evaluates a client-supplied false as though it were set. The same normalization applies to prompts/get arguments on versions 0.5.0 and later, while the practical impact is bounded: the client could have sent true directly, so only hosts or policy layers whose false branch diverges from their true branch are meaningfully affected, and an attacker must already be an authorized MCP client (CVSS 4.0 base 2.3; assessed CVSS 3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N). No public exploit has been identified at time of analysis and CISA SSVC records no exploitation; a vendor-released patch (0.10.1) is available.
Incorrect client-IP attribution inside the Brocade Fabric OS web management daemon lets an authenticated, adjacent-network attacker win a timing race and potentially slip past AAA evaluation or Calling-Station-ID ACL policies on switches running Fabric OS before 10.0.1. Because the PAM modules in the multi-threaded execution pool can pick up stale or mismatched client IP addresses and switch context numbers, audit records can be misattributed and IP-keyed policy decisions can be made against the wrong session. Impact is limited to integrity of low severity (CVSS 4.0 2.1 / assessed CVSS 3.1 5.0-style low), exploitation is probabilistic rather than reliable, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Race-condition information disclosure in Brocade Fabric OS before 10.0.1 allows a low-privilege authenticated attacker on an adjacent/management network to obtain limited management or configuration data belonging to another concurrent FCIP request. The issue requires precise timing to win the narrow window between address-variable population and response construction, making exploitation non-deterministic and limited to partial data exposure; no public exploit identified at time of analysis. With CVSS 2.1 and no integrity or availability impact, this is a low-priority information disclosure issue.
Heap buffer overflow in the MongoDB PHP Driver's BSON encoder can corrupt process memory or crash the PHP process when an application encodes a string near 4 GiB under a non-default runtime configuration that permits multi-gigabyte values. The vulnerability requires local access (AV:L) and low privileges (PR:L), and per the independent assessment, exploitation hinges on a specific attack requirement (AT:P) - the enabling configuration - making real-world risk low. No public exploit code or active exploitation (KEV) has been identified at time of analysis. The CVSS 4.0 base score is 2.0, and the independent CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L) confirms limited impact (low integrity and availability) with no confidentiality loss.