.NET
Monthly
Generation-time server-side request forgery, remote file inclusion and out-of-tree local file inclusion in the Refitter .NET tool (versions through 2.0.0) allow an attacker who controls or can influence an OpenAPI description to make the build host fetch arbitrary http(s) URLs or read files outside the input directory, with the retrieved content inlined into the generated C# Refit interfaces. Rated CVSS 3.1 7.1 (High) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N: unauthenticated and low complexity on the network side, but exploitable only when a developer or CI job actually runs refitter against the malicious spec, and the chain terminates at disclosure and SSRF - no code execution, because Refit sets the base URL at runtime, enum values are verbatim-string doubled and string defaults are escaped. A public reproduction script is attached to the upstream advisory and was verified by the reporter against 2.0.0; no CISA KEV entry appears in the supplied data, and the vendor fix ships in 2.1.1.
Identity impersonation in the MongoDB C#/.NET Driver allows one application user to execute database operations under another user's X.509 identity, affecting the confidentiality and integrity of everything that identity can reach. The driver's shared connection cache keys TLS client certificates only by issuer and serial number, so a user who copies a victim certificate's issuer and serial into their own certificate - without holding the victim's private key - can be handed a cached connection already authenticated as the victim. The flaw requires a specific multi-tenant architecture where one host application builds multiple clients from per-user certificates while sharing a connection pool; there is no public exploit identified at time of analysis, but the underlying patch is shipped in version 3.13.0.
Signals point to a real but bounded availability risk rather than a top-tier emergency: the MongoDB C# Driver's BSON library interns every BsonSymbol produced during deserialization and retains those symbols for the lifetime of the process with no cap, so an unauthenticated remote party able to get attacker-influenced BSON or JSON deserialized can drive unbounded memory growth and deny service to the host application (availability-only; assessed CVSS 3.1 AV:N/AC:H/PR:N/UI:N/C:N/I:N/A:H, CNA CVSS 4.0 score 8.2). Exposure is conditional - the application must actually deserialize untrusted content through the driver and that content must carry BSON symbol values; merely having the driver installed is not a trigger, and no MongoDB server component is affected. No public exploit code or confirmed active exploitation has been identified at time of analysis; version 3.13.0 removes symbol interning as the fix.
Unauthenticated remote denial of service against Microsoft .NET Framework and the System.Security.Cryptography.Xml library, caused by asymmetric resource consumption (CWE-405) during processing of attacker-supplied XML. The flaw carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H): any service that exposes XML signature parsing/verification to untrusted input, on affected builds of .NET Framework 3.5, 4.6.2/4.7/4.7.1/4.7.2, 4.8 below 4.8.4811.0 and 4.8.1 below 4.8.9363.0, or System.Security.Cryptography.Xml below 10.0.13, can be driven into resource exhaustion that degrades or halts the service. No public exploit code has been identified at time of analysis and it is not listed in CISA KEV; SSVC records Exploitation: none with Automatable: yes, indicating a technically reproducible, wormable-class DoS pattern rather than a currently observed campaign. Impact is limited to availability - no confidentiality or integrity loss and no code execution path.
Denial of service in Microsoft .NET Framework (versions 3.5 through 4.8.1) and the System.Security.Cryptography.Xml package allows a remote, unauthenticated attacker to exhaust server resources by submitting crafted input to an application that processes it through the vulnerable code path; the assessed vector is AV:N/AC:L/PR:N/UI:N with availability-only impact (C:N/I:N/A:H, CVSS 7.5), meaning no data disclosure and no code execution. The affected-component list points at XML and cryptographic-XML handling - for example XML signature verification or SAML-style document parsing - so internet-facing endpoints that accept such documents are the primary exposure. Microsoft has published a vendor advisory with fixed builds, and no public exploit has been identified at time of analysis (SSVC exploitation: none); CISA KEV does not list this CVE.
Authentication bypass in Microsoft .NET allows an unauthenticated, remote attacker to forge a cryptographic signature and have it accepted by applications that rely on the framework's signature-verification routines, potentially leading to unauthorized access or token misuse. The JWT Attack tag points to a token-signature validation weakness; exploitation requires the target application or user to process the attacker-supplied signed token (UI:R), which limits reachability for purely passive endpoints. Affected versions include .NET 10.0 before 10.0.402, .NET 11.0 before 11.0.100-rc.2, and the listed Visual Studio 2022 17.14.x/2026 18.10.x builds; vendor patches are available, and no public exploit identified at time of analysis.
Code execution in .NET and Visual Studio can be triggered when a developer or user processes attacker-supplied content - such as a crafted project, build input, or dependency - that pulls functionality in from an untrusted control sphere and executes it. Affected builds are .NET 8.0 before 8.0.132, .NET 9.0 before 9.0.319, .NET 10.0 before 10.0.113, Visual Studio 2022 17.14 before 17.14.42, and Visual Studio 2026 18.10 before 18.10.4; the issue is network-reachable and unauthenticated (PR:N) but requires user interaction (UI:R) and non-trivial preconditions (AC:H), so an attacker cannot silently trigger it remotely. There is no public exploit identified at time of analysis and no confirmed active exploitation - the CISA SSVC exploitation value is 'none' - which keeps this a moderate-priority issue rather than a drop-everything emergency despite the 7.5 High CVSS score, especially since the SSVC technical impact is assessed as 'total' once exploitation conditions are met.
Out-of-bounds write in Microsoft .NET 8.0, 9.0, 10.0, 11.0, and Visual Studio 2022/2026 can allow an unauthenticated remote attacker to execute code when a victim processes crafted input, per CVSS 3.1 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). This is a genuinely high-priority, patch-worthy flaw but with important caveats that lower its real-world urgency relative to its 8.8 CVSS: exploitation requires user or application interaction to process the malicious input, and no public exploit has been identified at time of analysis. Vendor-released patches are available as .NET 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2, plus Visual Studio 17.14.42 and 18.10.4.
An out-of-bounds write (CWE-787) in ASP.NET Core and the associated .NET runtimes lets a remote, unauthenticated attacker trigger memory corruption that crashes or destabilizes a network-reachable service, yielding a full loss of availability (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Exploitation requires no credentials, no user interaction, and no special configuration - only that the target endpoint be reachable and running an unpatched build (for example .NET 8.0 below 8.0.32, .NET 9.0 below 9.0.21, or .NET 10.0 below 10.0.13). There is no public exploit identified at time of analysis and CISA's SSVC rates exploitation as "none" while marking the flaw fully automatable, so scripted denial-of-service attempts remain a plausible near-term risk; vendor patches are available.
Local privilege escalation in the .NET runtime (8.0, 9.0, 10.0, and 11.0 preview) and in Visual Studio 2022 17.14 and Visual Studio 2026 18.10, which ship affected runtime builds, allows an authenticated local attacker to gain higher-privileged file access or code execution by crafting a symbolic or hard link that a more privileged .NET or IDE process later resolves. Exploitation requires prior low-privileged local access to the host and typically depends on winning a timing/race condition against a privileged process (CISA SSVC Automatable: no), which confines realistic risk to developer workstations, build servers, and CI agents rather than general end-user endpoints. The issue scores 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) with total technical impact, no public exploit has been identified at time of analysis, and vendor-released patches are available. This is a credible but not emergency-grade issue, best treated as routine-high patching priority rather than a drop-everything event.
Remote code execution in Microsoft .NET allows an unauthenticated attacker to execute arbitrary code when a legitimate user opens or loads crafted content that triggers an out-of-bounds write in the runtime. The flaw affects a broad range of .NET Framework versions (3.5 through 4.8.1), modern .NET 8.0, 9.0, 10.0, and 11.0 preview, plus Visual Studio 2022 and 2026. No public exploit code or active exploitation has been identified at time of analysis, and CISA SSVC rates the issue as non-automatable, though the mandatory user interaction and wide deployment make patching critical for unpatched systems.
Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) component of .NET, specifically runtimes 8.0.0 through 8.0.31, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, as well as Visual Studio 2022 17.14 and Visual Studio 2026 18.10 installations that carry the vulnerable runtime. An unauthenticated attacker can deliver crafted content that, when a victim interacts with an XPS document whose synthetic hyperlinks are exposed through UI Automation, bypasses the application's restrictive navigation checks and reaches attacker-controlled content, leading to code execution in the context of the running application; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms high confidentiality, integrity, and availability impact but explicitly requires user interaction. Vendor patches are available (runtime fixes 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2), and no public exploit code was identified at time of analysis despite the network-reachable attack path.
Unauthenticated remote attackers can drive CPU exhaustion in .NET applications that validate untrusted signed CMS/PKCS#7 data, because SignedCms.CheckSignature in the System.Security.Cryptography.Pkcs package repeatedly reparses attacker-controlled X.509 content at quadratic cost (CWE-407, CVSS 7.5, AV:N/AC:L/PR:N/UI:N with availability-only impact, C:N/I:N/A:H). Affected build ranges are System.Security.Cryptography.Pkcs 8.0.0 through 8.0.1, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, along with the listed .NET Framework 3.5 / 4.6.2 / 4.7 / 4.7.1 / 4.7.2 / 4.8 / 4.8.1 servicing baselines and Visual Studio 2022 17.14 and Visual Studio 2026 18.10. Exploitation is bounded to services that actually accept and cryptographically verify externally supplied signed CMS messages through this API; no public exploit identified at time of analysis, and CISA SSVC records exploitation as none.
Remote code execution in .NET WPF (Microsoft.WindowsDesktop.App.Runtime) allows an unauthenticated attacker to execute code on a victim's Windows system by crafting a malicious XAML/XPS document or serialized payload and convincing the user to open or load it. The vulnerability is a CWE-502 deserialization of untrusted data issue rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); exploitation requires user interaction and is not automatable (SSVC Automatable=no, Exploitation=none). No public exploit code or active exploitation has been identified at time of analysis, though vendor patches are available for all affected .NET and .NET Framework versions.
Memory corruption in Microsoft .NET's System.Net.Sockets component allows an unauthorized attacker to execute code over a network on Windows hosts, but only against applications that reuse a single SocketAsyncEventArgs instance across both IPv4 and IPv6 UDP datagram sockets. The flaw (CVSS 8.1, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) manifests as an out-of-bounds write in the ReceiveFromAsync path once an undersized cached native address buffer is retained; no authentication or user interaction is required, though the high attack complexity reflects the non-default coding pattern required to reach the vulnerable state. There is no public exploit identified at time of analysis, CISA SSVC records exploitation as none and non-automatable, and no KEV listing applies; Microsoft has shipped fixed runtime builds, making this a meaningful but non-emergency patching priority.
Path traversal in .NET (CWE-22) allows an authenticated local attacker to escape an intended restricted directory and elevate privileges on the host, with the same flaw reaching users through the Visual Studio 2022 17.14 and Visual Studio 2026 18.10 toolchains. Successful exploitation requires a local, already-authenticated foothold (PR:L) plus user interaction (UI:R), meaning a higher-privileged user or process must be induced to act on an attacker-influenced pathname; it is therefore not remotely triggerable, and CISA's SSVC assessment records Exploitation: none, Automatable: no, with total technical impact if it does succeed. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this rates as a moderate-priority local privilege-escalation issue rather than an urgent, widely exploitable threat. Vendor patches are available.
Denial of service in Microsoft .NET lets an unauthenticated remote attacker force the runtime into disproportionately expensive computation, driving CPU or memory consumption high enough to degrade or halt a service. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) confirms remote, low-complexity, unauthenticated exploitation with no user interaction and a high availability-only impact, requiring only that the vulnerable .NET code path be reachable by attacker-supplied network input - no public exploit code was identified at time of analysis and the issue is not listed in CISA KEV. Exposure is limited to reachable, .NET-based services; internal-only or non-.NET-facing deployments are not affected, and the exact affected runtime versions must be confirmed against the MSRC advisory.
Type confusion (CWE-843) in Microsoft .NET and Visual Studio allows an unauthenticated remote attacker to elevate privileges when a victim opens, loads, or builds attacker-supplied content in developer tooling, rated CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not zero-click: an attacker must socially engineer a developer into processing a malicious file, project, or package so the type-confusion code path is reached, and the practical limiting factor remains that user-interaction requirement. No CISA KEV entry, no public exploit code, and no EPSS data were provided at time of analysis, so this is a credible high-priority issue but with important caveats.
Hard-coded JWT signing key in BotSharp through 5.2.0 allows unauthenticated remote attackers to forge bearer tokens and impersonate any user, including administrators, on Authorize-protected API routes. Exploitation requires the deployment to retain the default key and default 'botsharp' issuer/audience; rotating these values mitigates the issue. No public exploit code has been identified at the time of analysis, but the high impact and low complexity make this a genuine high-priority risk as confirmed by independent assessment.
Memory corruption in SixLabors ImageSharp 4.0.0 through 4.1.1 allows an unauthenticated remote attacker to crash or destabilize a host process by supplying an image whose embedded ICC profile declares more than four LUT16 input/output channels, causing out-of-bounds writes past a four-float internal buffer. The flaw is only reachable when an application has explicitly set DecoderOptions.ColorProfileHandling to Convert, since the default Preserve mode does not run ICC conversion; the independent assessment scores it CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), reflecting an availability-only impact rather than data disclosure or modification. No public exploit code was identified at time of analysis, and the issue is fixed in version 4.1.2.
PKIX certificate path validation in the Bouncy Castle C# library (bc-csharp) before 2.7.0 accepts certificates whose subject distinguished name, or directoryName subjectAltName, falls outside a name-constrained intermediate CA's permitted subtrees, breaking the RFC 5280 name-constraint trust boundary. An unauthenticated attacker who controls, or can obtain certificates from, a name-constrained intermediate CA already present in a chain the victim validates can craft a DN that prepends extra RDNs ahead of a copy of the permitted RDN sequence and have it accepted by PkixNameConstraintValidator.WithinDNSubtree. Vendor-released patches are available in the 2.7.0 codebase (commits 606e9153b97a265c70ca8293d21ec859344d7de8 and 75c3c576602886180ed92a63c89419e3bd63b392), and no public exploit code has been identified at time of analysis; exploitation is gated by the precondition that a name-constrained CA must already be positioned in the validated chain, so environments that do not enforce directoryName name constraints are unaffected.
Denial of service in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows unauthenticated remote attackers to exhaust process memory by supplying crafted OpenPGP public keys, certificates, or signatures, because a subpacket header using the five-octet (0xFF) length form declares an oversized body length that is used directly to size a buffer before any subpacket data is read. The flaw lives in SignatureSubpacketsParser.ReadPacket and UserAttributeSubpacketsParser.ReadPacket (CWE-789, memory allocation with excessive size value) and is rated CVSS 4.0 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H) and an independently assessed CVSS 3.1 of A:H with no confidentiality or integrity impact; a handful of input bytes can demand an allocation of up to roughly 2 GB (the 32-bit length field permits up to ~4 GB in principle), so any service that imports or verifies untrusted PGP material is exposed. Vendor patches are available (bc-csharp 2.7.0) and no public exploit code has been identified at time of analysis, though the upstream regression test does illustrate the malicious packet format.
Crafted small-order or out-of-range Diffie-Hellman values passed to DHAgreement.CalculateAgreement in Bouncy Castle C# (bc-csharp) before 2.7.0 let an on-path attacker or malicious peer defeat the key authentication MTI/A0 is designed to provide and, when the local party reuses a static DH private key, learn that key modulo the small factors of p-1 - with full recovery possible in groups where p-1 has many small prime factors. The issue is unauthenticated (CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), and exploitation is not opportunistic: it works only where an application calls DHAgreement directly in an MTI/A0 two-pass flow, and it requires a protocol peer or on-path attacker able to inject a crafted 'message' or public-key value; higher-level Bouncy Castle protocol wrappers are unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and the independent assessment rates real-world blast radius as narrower than the 9.1 CVSS 4.0 base score suggests because of the narrow direct-caller API surface, the static-key reuse prerequisite, and the dependence on weak group parameters for complete key recovery.
On-path attackers who can intercept and modify CMS messages can silently tamper with AES-CCM-protected content that Legion of the Bouncy Castle Inc.'s bc-csharp library (versions before 2.7.0) decrypts. The root cause is that CcmParameters accepted any aes-ICVlen value from an untrusted AlgorithmIdentifier while CcmBlockCipher enforced the tag length only on the encryption path, so a decryption carrying a zero-length or very short tag compared an empty or truncated tag and accepted forged ciphertext without any detectable integrity failure; the same fix also hardens the AES-GCM CMS parameter handling. The reachable paths are ParameterUtilities.GetCipherParameters as used by CmsEnvelopedData and CmsEnvelopedDataParser for AES-CCM EnvelopedData, plus any caller that forwards an unchecked tag length into CcmBlockCipher for decryption. A vendor patch is available in 2.7.0 and the change is published as two commits plus a wiki advisory; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and because exploitation requires an attacker to already hold a network interception position (no remote-from-anywhere access, no authentication, no user interaction), the practical risk is a genuine but precondition-gated integrity/tampering issue rather than a broadly exploitable one.
Progress Software Fiddler Everywhere 8.0.2 ships a local .NET backend (Fiddler.WebUi) that exposes an HTTP and SignalR RPC endpoint on the loopback interface without any authentication, allowing any local user or process on the same machine to call privileged methods, mint OAuth tokens, and export the application's machine-in-the-middle root certificate. The issue is strictly local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, 7.7) and only exploitable while Fiddler Everywhere is installed and running, but it requires no credentials or user interaction once those conditions hold. There is no evidence of active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; the practical risk is credential and trust-anchor theft on shared workstations or hosts where untrusted local software can execute.
Argument injection in the CliInvoke .NET process-wrapping library (and its former identity, AlastairLundy.CliInvoke) allows a double quote in a caller-supplied target or argument to break out of the operating-system-level quoted region and add unintended elements to a runner's argument vector, potentially escalating to arbitrary command execution when a shell runner is used. Affected versions span CliInvoke 2.0.0-2.8.4, 2.9.0-2.9.3, 2.10.0-2.10.4 and 3.0.0-alpha.1-3.0.0-beta.1, plus AlastairLundy.CliInvoke 2.0.0-alpha.1-2.0.0; the flaw is reachable only when a consuming .NET application routes attacker-influenced data through RunnerProcessFactory (2.x) or RunnerConfigurationFactory (3.x) instead of building a ProcessConfiguration with an explicit ArgumentList. Scored CVSS 3.1 8.4 (High) with vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, it carries no public exploit identified at time of analysis and is not in CISA KEV.
Malformed service-registry records can blank out service discovery for Steeltoe-based cloud-native applications: EurekaDiscoveryClient versions 4.0.0 through 4.2.x deserialize the entire Eureka registry response as one atomic unit, so a single instance entry with an unrecognized actionType or status, a non-Boolean isCoordinatingDiscoveryServer, or a nonnumeric timestamp aborts the whole payload and leaves every connected client with an empty or stale instance list. The vendor rates this 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) while the independent assessment rates the vector with PR:L and scope changed, reflecting that a practical attacker must be a principal able to register or update an instance in the Eureka registry that victim clients consume; impact is availability-only, with no data exposure or code execution, and the effect self-heals once the bad registration is removed. No public exploit code has been identified at time of analysis and the issue is fixed in Steeltoe 4.3.0.
Consul service discovery in Steeltoe 4.0.0 through 4.2.x can be rendered persistently unusable by a single malformed service registration, because ConsulServiceInstance parses the registration's 'secure' metadata with a strict Boolean conversion that throws on any value other than 'true' or 'false'. A principal able to write to the Consul catalog - i.e. holding a valid ACL token with service-registration rights, or reaching a Consul deployment that runs without ACLs - can register a service whose 'secure' metadata is set to a value such as 'yes', '1' or an empty string; the resulting exception aborts construction of the instance list, and because GetAllInstancesAsync throws on the first bad entry, enumeration of every discovered service fails, taking the target (or the entire discovery surface) offline until the offending registration is removed. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (the advisory's vector differs only in reporting PR:N instead of PR:L), and while no public exploit code has been identified at time of analysis, no CISA KEV entry exists, and no EPSS score was supplied, the impact is low-complexity and requires no user interaction, so Consul catalog write access should be treated as a denial-of-service primitive.
SQL injection (CWE-89) in Marten, the .NET transactional document DB and event store for PostgreSQL, affects versions 7.0.0 through 9.12.x and lets an authenticated attacker who can influence strings reaching Marten's LINQ or tenant-management paths break out of single-quoted SQL/JSON-path literals and inject an always-true predicate, causing filter or multi-tenant authorization bypass and blind data exfiltration; on deployments that permit semicolon-batched Npgsql statements, data modification is also possible. The primary confirmed vector is a dictionary indexer key used in Where filters (src/Marten/Linq/Members/Dictionaries/DictionaryItemMember.cs); Dictionary.ContainsKey is exploitable only under the Newtonsoft serializer, tenant identifiers reaching DeleteAllForTenant.cs via IEventStore.DeleteProjectionProgressAsync are likewise affected, and EventLoader.cs contains a related defense-in-depth sink. The vendor confirmed the issue in GHSA-rfx3-98h7-v3xp and fixed it in version 9.13.0 via PR #4911; no public exploit code was identified at time of analysis, and exploitation requires the host application to route attacker-controlled strings into one of these Marten paths.
XML external entity (XXE) injection in the IBM MQ .NET client allows an authenticated attacker with queue-write access to read files from the host running that client and to cause a limited denial of service when the client parses the RFH2 folder of a crafted message. The flaw is client-side - the queue manager itself and the Java/C clients are not indicated as affected - and the attacker must already hold valid MQ credentials with authority to place messages on a queue the vulnerable client consumes. No public exploit has been identified at time of analysis, CISA's SSVC assessment records no exploitation activity and rates the issue not automatable with partial technical impact, and patch code is available from the vendor; the practical risk is genuine but moderate, well below what the 7.1 base score suggests at first glance.
Privilege elevation in Microsoft Visual Studio 2022 (17.14.0 to <17.14.40), Visual Studio 2026 (18.9.0 to <18.9.3), and the Microsoft.Diagnostics.Runtime (ClrMD) library stems from external control of a file name or path (CWE-73) that a higher-privileged process then resolves without canonicalization, letting an unauthenticated remote attacker influence which file is opened or executed and thereby gain the privileges of the resolving process. The assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CVSS 8.1) confirms no authentication or user interaction is required, but the high attack-complexity rating reflects that success depends on specific input conditions and on whether the affected developer/diagnostics component actually consumes attacker-influenced paths in a given deployment. Risk signals are mixed: EPSS is only 0.51% (42nd percentile), CISA SSVC records Exploitation: none and Automatable: no, and no public exploit code has been identified at time of analysis, so this is a high-severity but not high-urgency issue; vendor patches are available and the affected components are developer tooling rather than always-on network services.
The OpenTelemetry .NET OTLP exporter's experimental disk-retry feature can be abused by an authenticated local attacker when `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk` is set without `OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH`, causing retry blobs to be written to and read from fixed `traces`, `metrics` and `logs` subdirectories under the shared system temp root. An attacker holding a separate local account with read/write access to that temp directory can inject crafted `*.blob` files that the exporter later forwards to the configured OTLP endpoint under the application's identity and credentials, read the application's own serialized telemetry blobs, or flood the retry loop with oversized files to degrade performance and consume disk. The affected NuGet package is `OpenTelemetry.Exporter.OpenTelemetryProtocol` from 1.8.0 through 1.15.2 and is fixed in 1.15.3; the feature is experimental and off by default, exposure only arises when the directory variable is omitted, and no public exploit code was identified at time of analysis (EPSS 0.01%, no KEV entry), so risk is real but conditional on shared-temp multi-user hosts.
Insecure .NET Remoting deserialization in Altec DocLink (Beyond Limits) 4.0.336.0. Exposed TCP endpoints allow unauthenticated remote code execution via .NET Remoting deserialization attacks.
Configuration injection in OpenClaw Docker sandbox before 2026.2.15 allows escaping sandbox restrictions. Patch available.
Static ASP.NET machineKey in Calero VeraSMART before 2022 R1. Hardcoded key enables ViewState deserialization attacks and cookie forgery.
Unauthenticated .NET Remoting endpoint in Calero VeraSMART before 2022 R1. TCP port 8001 exposes default Object URIs enabling deserialization attacks. EPSS 0.17%.
.NET applications are vulnerable to spoofing attacks due to improper validation of a required security element, allowing unauthenticated remote attackers to forge or manipulate application data over the network. This vulnerability affects multiple .NET versions and currently has no available patch, exposing organizations to authentication bypass and data integrity risks. The attack requires no user interaction and can be exploited directly from the network.
PowerDocu versions prior to 2.4.0 allow arbitrary .NET object instantiation and code execution through unsafe deserialization of the $type property in JSON files within Flow or App packages. A local attacker with user interaction can exploit this vulnerability to achieve full system compromise. Public exploit code exists for this vulnerability, and no patch is currently available for affected versions.
Microsoft Semantic Kernel SDK has a CVSS 9.9 path traversal vulnerability enabling AI agents to access arbitrary files outside their intended scope.
DNN (DotNetNuke) CMS has a stored XSS vulnerability (CVSS 9.1) allowing persistent script injection that executes for all users viewing the affected content.
Stored cross-site scripting in DNN versions 9.0.0 through 9.13.9 and 10.0.0 through 10.1.x allows high-privileged users with UI interaction to inject malicious scripts into module friendly names that execute within the Persona Bar administrative interface. An authenticated attacker with sufficient permissions could exploit this to perform administrative actions or compromise other users' sessions. No patch is currently available for affected versions.
Stored cross-site scripting in DNN versions 9.0.0 through 9.13.9 and 10.0.0 through 10.1.x allows authenticated administrators with high privileges to inject malicious scripts into log notes that execute within the PersonaBar interface. An attacker with admin credentials could perform actions as the victim or steal session data when the logs are viewed. Upgrade to DNN 9.13.10 or 10.2.0 to remediate this vulnerability.
DotNetNuke versions prior to 9.13.10 and 10.2.0 allow arbitrary script execution in the Persona Bar administrative interface through unsanitized richtext content in module descriptions. An authenticated attacker with module installation privileges can inject malicious scripts that execute in the context of administrative users, potentially compromising sensitive data or administrative functions. This vulnerability requires high privileges and user interaction to exploit, with no public patch currently available for affected versions.
Client-side field-level encryption (CSFLE) in the MongoDB .NET/C# driver silently writes fields that should have been encrypted as plaintext when the process runs under certain platform text-encoding configurations, because an internal name conversion loses information and the operation is never matched to its configured encryption rules. Affected are driver versions from 2.10.0 up to but not including 3.13.0, and only deployments that actually have CSFLE configured and in use; an application user able to write data through such an application can cause sensitive fields to be persisted unencrypted with no error raised. There is no integrity or availability impact, no public exploit identified at time of analysis, and the issue is resolved in driver release 3.13.0.
Improper authentication in the dotnet eShop Catalog API's AddApplicationServices configuration lets unauthenticated remote attackers bypass authentication controls and achieve limited confidentiality, integrity, and availability impact on catalog data; affected builds are up to commit 913acea66708a59595351174cee9b29f37179d29. The CVSS v4 vector records Proof-of-Concept exploit maturity (E:P), so publicly available exploit code exists, but there is no confirmed active exploitation (not in CISA KEV). Because eShop is a Microsoft reference/sample application rarely exposed in production, practical risk is moderate and bounded to low-impact catalog-level effects.
Oqtane Framework through 10.2.6 exposes one tenant's stored private settings to the administrator of another tenant, allowing an authenticated site administrator to retrieve SMTPPassword and SMTPClientSecret values by requesting a foreign site's entityId through their own site alias. The flaw is an authorization bypass in SettingController (CWE-639, user-controlled key), scored 6.9 Medium under CVSS 4.0 (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N) and assessed as CVSS 3.1 6.0-style confidentiality-only impact (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N). Exploitation requires a multi-tenant Oqtane deployment hosting more than one site plus the attacker already holding the Administrators role on at least one tenant site; single-site installations are unaffected, no public exploit identified at time of analysis, and the impact is limited to credential disclosure with no integrity, availability, or code-execution effect (vendor advisory: https://www.vulncheck.com/advisories/oqtane-framework-through-10.2.6-cross-site-settings-disclosure-via-setting-api).
Denial of service in MessagePack-CSharp occurs when an application deserializes attacker-controlled MessagePack data into System.Object through PrimitiveObjectFormatter: the formatter allocates an object[] sized from each declared array length before the configured object-graph depth limit is applied, and nested array headers can reuse the same trailing unread bytes to satisfy per-header length validation, so a small payload (reported ~31.5 KiB) can hold roughly 114.7 MiB of reference storage live at once and, with repeated submissions, cause severe managed-heap pressure, excessive garbage collection, process termination, or loss of service. Affected releases are all MessagePack-CSharp versions before 2.5.303 and 3.x versions from 3.0.0 up to but excluding 3.1.9 (2.5.302 is confirmed vulnerable), with the named concrete exposure being an ASP.NET Core SignalR application that has AddMessagePackProtocol() enabled and a reachable hub method taking an object parameter. The CVSS vector is AV:N/AC:L/PR:N/UI:N with availability-only impact (C:N/I:N/A:L), so publicly reachable endpoints need no credentials while protected endpoints keep their existing authorization; exploitation requires repeated attacker-controlled submissions rather than a single request, and no public exploit code was identified at time of analysis.
Authenticated attackers with read and metadata-write access to encrypted objects in Amazon S3 can force a padding downgrade in the Amazon.Extensions.S3.Encryption .NET client, then use a Bleichenbacher padding oracle to recover the RSA-wrapped envelope key and decrypt the object. Affected versions are before 3.2.2 and 4.0.x before 4.0.3; the 1.x and 2.x lines are unpatched and must be migrated. Exploitation requires valid credentials, metadata modification permissions, and many decryption queries, so no public exploit identified at time of analysis, consistent with SSVC Exploitation: none.
Origin-validation bypass in Microsoft .NET 8.0, 9.0, 10.0 and 11.0 (plus bundled Visual Studio 2022 17.14 and Visual Studio 2026 18.10 builds) lets an unauthenticated remote attacker defeat a built-in security feature when a victim interacts with attacker-supplied cross-origin content, producing integrity-only impact (CVSS 6.5, I:H with no confidentiality or availability loss). The mandatory user-interaction step (UI:R) and the fact that exploitation depends on the application actually relying on the affected origin-checking feature keep this at moderate severity; there is currently no public exploit identified at time of analysis, CISA SSVC records exploitation as none and automation as no, and EPSS/KEV data is absent. Vendor patches are available (MSRC advisory msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96238).
Information disclosure in the Windows Desktop Runtime (WPF) component of .NET allows a remote, unauthenticated attacker to read data from a victim's machine when the victim opens or navigates a crafted XAML or XPS document - or content that causes WPF to fetch a remote URI or TrueType font - inside a WPF-based desktop application on Windows. Per the independent assessment, exploitation is constrained by mandatory user interaction (UI:R) and high attack complexity (AC:H) tied to specific conditions in the XAML/XPS parsing and hyperlink-navigation path, and no public exploit code or confirmed active exploitation has been identified at time of analysis, keeping real-world priority low-to-moderate despite the CVSS 5.3 moderate rating and high confidentiality impact. Affected builds span .NET 8.0, 9.0, 10.0 and 11.0 previews as well as Visual Studio 2022 17.14 and Visual Studio 2026 18.10, which ship the vulnerable runtime.
Use-after-free in the Microsoft QUIC (MsQuic) Schannel native library allows an unauthenticated, remote attacker who can reach a QUIC/HTTP-3 endpoint to disclose memory contents over the network, with impact limited to confidentiality (no integrity or availability effect). Affected software includes .NET applications referencing the Microsoft.Native.Quic.MsQuic.Schannel package in versions 1.9.0 through 2.6.1, plus a broad set of Windows 11 and Windows Server 2022/2025 builds and Visual Studio 2022/2026 that ship the vulnerable QUIC binaries. Exploitation is non-deterministic because the CVSS vector (AC:H) reflects a race condition the attacker must win, and no public exploit code has been identified at time of analysis; the CISA SSVC assessment records exploitation as none and the issue as not automatable, making this a genuine-but-moderate risk rather than a fire-drill.
Improper certificate validation in .NET 11's System.Net.Security component allows a remote, unauthenticated attacker to bypass mutual TLS authentication, because post-handshake TLS client authentication can fail to verify the client certificate. Only pre-release .NET 11 builds (11.0.0-preview.1 through 11.0.0-rc.1) running on Linux or macOS are affected, and exposure requires the application to use post-handshake mTLS client-certificate authentication with a server that is configured to require client certificates. No public exploit code has been identified at time of analysis, and remediation is available in .NET 11.0.0-rc.2, Visual Studio 2026 18.10.4, and Visual Studio 2022 17.14.42.
A pre-authentication denial-of-service condition in the .NET cryptographic library System.Security.Cryptography.Pkcs causes CPU exhaustion on Windows when `EnvelopedCms.Decode` processes specially crafted CMS/PKCS#7 attribute sets, because the decoding routine performs quadratic work proportional to the number of attacker-supplied attributes rather than linear work. Affected applications are Windows-hosted .NET apps that reference a vulnerable package version (8.0.0-8.0.1, 9.0.0-9.0.20, 10.0.0-10.0.12, or 11.0.0-preview.1 through 11.0.0-rc.1) and pass untrusted PKCS#7/CMS enveloped data into the decode path - a pattern common in S/MIME mail gateways, signed-message web endpoints, and certificate/token processing services; there is no impact to confidentiality or integrity (CVSS 5.9, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-405). Exploitation requires no authentication or user interaction but is constrained by the Windows-only scope, the requirement that the vulnerable CMS decode path actually be reachable from untrusted input, and high attack complexity (AC:H) needed to tune payloads for meaningful amplification; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', and no public exploit identified at time of analysis, though vendor-released patches are available. Visual Studio 2022 (17.14.0-17.14.41) and Visual Studio 2026 (18.10.0-18.10.3) installations that bundle the affected SDK/runtime are also in scope.
Information disclosure in .NET's System.Net.Http affects applications that use SocketsHttpHandler with an authenticating proxy, because the Proxy-Authorization header is retained when an outbound request is redirected and is then sent to the redirect destination, exposing Basic proxy credentials to a server the attacker can observe or control. Affected runtimes are .NET 8.0 before 8.0.32, 9.0 before 9.0.21, 10.0 before 10.0.13 and 11.0 before 11.0.0-rc.2, with Visual Studio 2022 17.14 before 17.14.42 and Visual Studio 2026 18.10 before 18.10.4 shipping the same component; the CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (5.9), reflecting high attack complexity rather than any authentication requirement. There is no public exploit identified at time of analysis - CISA's SSVC assessment rates exploitation as none and automatable as no - but the severity comes from a leaked credential, not from any integrity or availability impact, and the exposure is limited to the proxy secret rather than general application data.
Log-integrity tampering in the RemoteSyslogAppender of Apache log4net affects versions from 1.2.12 up to but not including 3.5.0, where characters outside the visible ASCII range are silently deleted from syslog records instead of being escaped. An unauthenticated remote party who can influence a value that reaches a log message (for example, a username containing a zero-width space) can make a distinct value appear identical to another in the audit record, such as a user name being logged as 'admin'. Only applications that explicitly configure RemoteSyslogAppender are affected; deployments using file, console, or other appenders are not. Impact is limited to integrity of the log record (CVSS I:L) with no confidentiality or availability effect, and no public exploit has been identified at time of analysis.
Improper handling of Unicode encoding in Apache log4net's SmtpPickupDirAppender lets an attacker who can place unencodable content - such as an unpaired UTF-16 surrogate like U+D800 - into a logged message break the appender's file writer, causing the entire buffered batch of logging events to be discarded rather than just the offending event, and leaving a truncated mail file in the pickup directory for the mail service to send. Only applications configured to use SmtpPickupDirAppender (the SMTP pickup-directory appender) with event buffering are affected; versions from 1.2.9 before 3.5.0 are impacted. The issue is rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) - remote and unauthenticated once attacker data reaches a rendered log field - but impact is confined to integrity of log output (suppression/truncation of audit records), with no confidentiality or availability loss; no public exploit code was identified at time of analysis and it is not confirmed actively exploited (not in CISA KEV).
Field level encryption can be silently disabled in applications built on the MongoDB Entity Framework Core Provider when the connection string places a database name there, causing sensitive fields to be stored or read without the intended protection. This affects only applications that rely on field level encryption to protect sensitive data; deployments not using FLE are unaffected. The attacker must already have read access to the MongoDB datastore, backups, or network traffic to benefit, and no public exploit identified at time of analysis. The CVE feed lists CVSS 6.8, while the independent assessment rates it as a conditional data-protection weakness (CWE-311), not a remote code-execution flaw.
Sensitive credential disclosure in the MongoDB Entity Framework Core Provider occurs when the application runs with DEBUG-level logging enabled or when a malformed MongoDB connection string is supplied, causing the provider to record the connection string - including any embedded passwords and AWS secret access keys, where used - into application logs. Realistic exploitation requires local access plus existing privileges sufficient to read those logs, and it is confined to non-default configurations; deployments that obtain credentials from IAM roles or secret managers rather than inline connection strings are largely unaffected. No public exploit has been identified at time of analysis, and this is a genuine but low-to-moderate priority information-disclosure flaw rather than an urgent one.
MongoDB EF Core silently drops TLS and schema-map (client-side field-level/queryable encryption field map) settings when an application configures encryption both through independent/application-level settings and through the provider's own encryption settings, causing fields that were meant to be encrypted to be persisted in the database as cleartext. Only .NET applications built on the MongoDB Entity Framework Core Provider that combine both encryption configuration paths are affected; deployments using a single path, or not using field encryption at all, are not affected. No public exploit identified at time of analysis - the flaw is a silent misconfiguration with no attacker interaction at write time, and actual disclosure additionally requires a party to gain read access to the underlying MongoDB data, backups, or logs (CWE-311, Missing Encryption of Sensitive Data).
Authentication bypass in Steeltoe.Security.Authorization.Certificate (Steeltoe prior to 4.3.0) lets remote unauthenticated attackers spoof the X-Client-Cert header to defeat the SameOrg and SameSpace authorization policies, gaining access to resources belonging to another organization or space. The flaw is that AddOrgAndSpacePolicies() combined with UseCertificateAuthorization() trusts a client-supplied public certificate without verifying proof of possession of the matching private key, and common Cloud Foundry routers pass the header through to the application. Exploitation is unauthenticated (PR:N) but high complexity (AC:H) and only succeeds when ingress does not restrict inbound traffic to a known trusted proxy source IP and the attacker already holds the public certificate of an application instance in the target org or space; there is no public exploit code and no CISA KEV entry, and EPSS data was not provided, so the practical risk is moderate and deployment-dependent. Fixed in Steeltoe 4.3.0.
Information disclosure in Steeltoe's Management Endpoint actuator (Steeltoe.Management.Endpoint) prior to 4.3.0 allows an unauthenticated remote attacker who can reach the exposed /actuator/httpexchanges endpoint to harvest secrets that were previously captured in recorded request query strings - OAuth and password-reset tokens, API keys, and signed-URL signatures - because MaskedUri only redacts URI user-info and never inspects the query string. The same recorded URIs are written by the Steeltoe.Management.Endpoint.Actuators.HttpExchanges DEBUG logger, giving anyone with log access a second disclosure channel. Exploitation is config-gated (IncludeQueryString must be enabled, the endpoint must be explicitly exposed, and prior traffic must actually have carried query-string secrets), scoring CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/C:H/I:N/A:N); no public exploit identified at time of analysis, and the issue is remediated in Steeltoe 4.3.0.
Asp.Net-Core-Inventory-Order-Management-System versions up to 9.20250118. contains a security vulnerability (CVSS 6.3).
NanaZip versions 5.0.1252.0 through 6.5.1637.x contain an integer underflow in the .NET Single File Application parser that allows local attackers with user privileges to cause denial of service through unbounded memory allocation when opening a specially crafted archive file. Public exploit code exists for this vulnerability. Patches are available in versions 6.0.1638.0 and 6.5.1638.0.
Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disclose in-process memory or trigger application crashes by crafting malicious .NET Single File Application bundles with malformed manifest headers. Public exploit code exists for this vulnerability, and patches are available in versions 6.0.1638.0 and 6.5.1638.0. The issue affects Dotnet and Nanazip products where a malicious user interaction with crafted archive files can bypass bounds checking during manifest parsing.
The Print Service component of Fiserv Originate Loans Peripherals (formerly Velocity Services) in unsupported version 2021.2.4 (build 4.7.3155.0011) uses deprecated .NET Remoting TCP channels that allow unsafe deserialization of untrusted data.
NanaZip versions 5.0.1252.0 through 6.0.1629.0 contain an out-of-bounds heap read in the .NET Single File bundle parser that can crash the application or expose sensitive heap memory when processing malicious archive files. A local attacker with user privileges can exploit this vulnerability by crafting a specially formatted file, and public exploit code is currently available. No patch is yet available for affected users.
SD.NET RIM versions before 4.7.3c contain a SQL injection vulnerability that allows attackers to inject malicious SQL statements through POST parameters 'idtyp' and 'idgremium'. [CVSS 8.2 HIGH]
Htmlsanitizer versions up to 9.0.892 is affected by improper encoding or escaping of output (CVSS 6.1).
DotNetNuke 9.5 contains a persistent cross-site scripting vulnerability that allows normal users to upload malicious XML files with executable scripts through journal tools. [CVSS 6.4 MEDIUM]
Stored cross-site scripting in DNN versions 9.0.0 through 10.1.x allows content editors to inject malicious scripts into module headers and footers that execute in the browsers of other users. An authenticated editor with content creation privileges can exploit this to steal session tokens, perform actions on behalf of other users, or redirect them to malicious sites. Updates to version 9.13.10 or 10.2.0 are required to remediate the vulnerability.
Exos 9300 instances are using a randomly generated database password to connect to the configured MSSQL server. The password is derived from static random values, which are concatenated to the hostname and a random string that can be read by every user from the registry.
The PeachPay - Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability checks on the ConvesioPay webhook REST endpoint in all versions up to, and including, 1.119.8. [CVSS 5.3 MEDIUM]
Changjetong T+ (through 16.x) has .NET deserialization RCE in an AjaxPro endpoint. Attacker-controlled JSON triggers deserialization of malicious .NET types. PoC available.
Entrust Instant Financial Issuance (IFI) On Premise software (formerly referred to as CardWizard) versions 5.x, prior to 6.10.5, and prior to 6.11.1 contain an insecure .NET Remoting exposure in the SmartCardController service (DCG.SmartCardControllerService.exe).
AWS SDK for .NET works with Amazon Web Services to help build scalable solutions with Amazon S3, Amazon DynamoDB, Amazon Glacier, and more. From versions 4.0.0 to before 4.0.3.3, Customer applications could be configured to improperly route AWS API calls to non-existent or non-AWS hosts. This notification is related to the use of specific values for the region input field when calling AWS services. An actor with access to the environment in which the SDK is used could set the region input fie...
Remote code execution in the ActiveMQ NMS AMQP .NET client affects all releases up to and including 2.3.0 when the client initiates an AMQP session to an attacker-controlled, compromised, or otherwise untrusted broker; that server can return crafted serialized data the client deserializes without bounds, potentially executing arbitrary code on the client host. The primary prerequisite is control or impersonation of the broker endpoint the client connects to, so deployments that only talk to trusted, internally controlled brokers are not realistically exploitable without first compromising that broker or the network path, and the allow/deny-list deserialization restriction added in 2.1.0 is bypassable so enabling it does not guarantee protection. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); EPSS is 2.09% (81st percentile) and the vendor-released fix is version 2.4.0.
Unauthenticated remote attackers can connect to a TLS-enabled Akka.Remote cluster without presenting a client certificate and fully participate in cluster communication, because Akka.Remote never requested the connecting peer's certificate in versions 1.2.0 through 1.5.51 - mutual TLS was simply not implemented. Any deployment that enabled TLS via the akka.remote.dot-netty.tcp transport to secure remoting and is reachable by untrusted parties is affected, yielding high confidentiality and integrity impact (CVSS 3.1 9.3 from the vendor; independent assessment scores AV:N/AC:L/PR:N/UI:N with C:H/I:H/A:N). There is no public exploit code identified at time of analysis and EPSS is low (0.31%, ~22nd percentile), but impact is deployment-conditional: clusters confined to a fully trusted private network, or that never enabled TLS, see no practical risk. Untrusted parties on the network path can obtain a position to join the cluster and exchange messages.
CVE-2025-30399 is an untrusted search path vulnerability in .NET and Visual Studio that allows unauthenticated remote attackers to execute arbitrary code through a network vector, requiring user interaction. The vulnerability affects multiple versions of .NET Framework and Visual Studio across Windows platforms. While the CVSS score is 7.5 (high), the attack complexity is high and requires user interaction, potentially limiting real-world exploitation frequency.
Critical authentication bypass vulnerability in ArchiverSpaApi ASP.NET applications caused by hard-coded JWT signing keys. An unauthenticated remote attacker can forge valid JWT tokens to bypass authentication and gain unauthorized access to protected API endpoints, potentially leading to data exfiltration, modification, or denial of service. The CVSS 8.1 score reflects high confidentiality, integrity, and availability impact, though the attack complexity is rated as high, suggesting some technical prerequisites.
Weak authentication in ASP.NET Core & Visual Studio allows an unauthorized attacker to elevate privileges over a network. [CVSS 7.0 HIGH]
Generation-time server-side request forgery, remote file inclusion and out-of-tree local file inclusion in the Refitter .NET tool (versions through 2.0.0) allow an attacker who controls or can influence an OpenAPI description to make the build host fetch arbitrary http(s) URLs or read files outside the input directory, with the retrieved content inlined into the generated C# Refit interfaces. Rated CVSS 3.1 7.1 (High) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N: unauthenticated and low complexity on the network side, but exploitable only when a developer or CI job actually runs refitter against the malicious spec, and the chain terminates at disclosure and SSRF - no code execution, because Refit sets the base URL at runtime, enum values are verbatim-string doubled and string defaults are escaped. A public reproduction script is attached to the upstream advisory and was verified by the reporter against 2.0.0; no CISA KEV entry appears in the supplied data, and the vendor fix ships in 2.1.1.
Identity impersonation in the MongoDB C#/.NET Driver allows one application user to execute database operations under another user's X.509 identity, affecting the confidentiality and integrity of everything that identity can reach. The driver's shared connection cache keys TLS client certificates only by issuer and serial number, so a user who copies a victim certificate's issuer and serial into their own certificate - without holding the victim's private key - can be handed a cached connection already authenticated as the victim. The flaw requires a specific multi-tenant architecture where one host application builds multiple clients from per-user certificates while sharing a connection pool; there is no public exploit identified at time of analysis, but the underlying patch is shipped in version 3.13.0.
Signals point to a real but bounded availability risk rather than a top-tier emergency: the MongoDB C# Driver's BSON library interns every BsonSymbol produced during deserialization and retains those symbols for the lifetime of the process with no cap, so an unauthenticated remote party able to get attacker-influenced BSON or JSON deserialized can drive unbounded memory growth and deny service to the host application (availability-only; assessed CVSS 3.1 AV:N/AC:H/PR:N/UI:N/C:N/I:N/A:H, CNA CVSS 4.0 score 8.2). Exposure is conditional - the application must actually deserialize untrusted content through the driver and that content must carry BSON symbol values; merely having the driver installed is not a trigger, and no MongoDB server component is affected. No public exploit code or confirmed active exploitation has been identified at time of analysis; version 3.13.0 removes symbol interning as the fix.
Unauthenticated remote denial of service against Microsoft .NET Framework and the System.Security.Cryptography.Xml library, caused by asymmetric resource consumption (CWE-405) during processing of attacker-supplied XML. The flaw carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H): any service that exposes XML signature parsing/verification to untrusted input, on affected builds of .NET Framework 3.5, 4.6.2/4.7/4.7.1/4.7.2, 4.8 below 4.8.4811.0 and 4.8.1 below 4.8.9363.0, or System.Security.Cryptography.Xml below 10.0.13, can be driven into resource exhaustion that degrades or halts the service. No public exploit code has been identified at time of analysis and it is not listed in CISA KEV; SSVC records Exploitation: none with Automatable: yes, indicating a technically reproducible, wormable-class DoS pattern rather than a currently observed campaign. Impact is limited to availability - no confidentiality or integrity loss and no code execution path.
Denial of service in Microsoft .NET Framework (versions 3.5 through 4.8.1) and the System.Security.Cryptography.Xml package allows a remote, unauthenticated attacker to exhaust server resources by submitting crafted input to an application that processes it through the vulnerable code path; the assessed vector is AV:N/AC:L/PR:N/UI:N with availability-only impact (C:N/I:N/A:H, CVSS 7.5), meaning no data disclosure and no code execution. The affected-component list points at XML and cryptographic-XML handling - for example XML signature verification or SAML-style document parsing - so internet-facing endpoints that accept such documents are the primary exposure. Microsoft has published a vendor advisory with fixed builds, and no public exploit has been identified at time of analysis (SSVC exploitation: none); CISA KEV does not list this CVE.
Authentication bypass in Microsoft .NET allows an unauthenticated, remote attacker to forge a cryptographic signature and have it accepted by applications that rely on the framework's signature-verification routines, potentially leading to unauthorized access or token misuse. The JWT Attack tag points to a token-signature validation weakness; exploitation requires the target application or user to process the attacker-supplied signed token (UI:R), which limits reachability for purely passive endpoints. Affected versions include .NET 10.0 before 10.0.402, .NET 11.0 before 11.0.100-rc.2, and the listed Visual Studio 2022 17.14.x/2026 18.10.x builds; vendor patches are available, and no public exploit identified at time of analysis.
Code execution in .NET and Visual Studio can be triggered when a developer or user processes attacker-supplied content - such as a crafted project, build input, or dependency - that pulls functionality in from an untrusted control sphere and executes it. Affected builds are .NET 8.0 before 8.0.132, .NET 9.0 before 9.0.319, .NET 10.0 before 10.0.113, Visual Studio 2022 17.14 before 17.14.42, and Visual Studio 2026 18.10 before 18.10.4; the issue is network-reachable and unauthenticated (PR:N) but requires user interaction (UI:R) and non-trivial preconditions (AC:H), so an attacker cannot silently trigger it remotely. There is no public exploit identified at time of analysis and no confirmed active exploitation - the CISA SSVC exploitation value is 'none' - which keeps this a moderate-priority issue rather than a drop-everything emergency despite the 7.5 High CVSS score, especially since the SSVC technical impact is assessed as 'total' once exploitation conditions are met.
Out-of-bounds write in Microsoft .NET 8.0, 9.0, 10.0, 11.0, and Visual Studio 2022/2026 can allow an unauthenticated remote attacker to execute code when a victim processes crafted input, per CVSS 3.1 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). This is a genuinely high-priority, patch-worthy flaw but with important caveats that lower its real-world urgency relative to its 8.8 CVSS: exploitation requires user or application interaction to process the malicious input, and no public exploit has been identified at time of analysis. Vendor-released patches are available as .NET 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2, plus Visual Studio 17.14.42 and 18.10.4.
An out-of-bounds write (CWE-787) in ASP.NET Core and the associated .NET runtimes lets a remote, unauthenticated attacker trigger memory corruption that crashes or destabilizes a network-reachable service, yielding a full loss of availability (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). Exploitation requires no credentials, no user interaction, and no special configuration - only that the target endpoint be reachable and running an unpatched build (for example .NET 8.0 below 8.0.32, .NET 9.0 below 9.0.21, or .NET 10.0 below 10.0.13). There is no public exploit identified at time of analysis and CISA's SSVC rates exploitation as "none" while marking the flaw fully automatable, so scripted denial-of-service attempts remain a plausible near-term risk; vendor patches are available.
Local privilege escalation in the .NET runtime (8.0, 9.0, 10.0, and 11.0 preview) and in Visual Studio 2022 17.14 and Visual Studio 2026 18.10, which ship affected runtime builds, allows an authenticated local attacker to gain higher-privileged file access or code execution by crafting a symbolic or hard link that a more privileged .NET or IDE process later resolves. Exploitation requires prior low-privileged local access to the host and typically depends on winning a timing/race condition against a privileged process (CISA SSVC Automatable: no), which confines realistic risk to developer workstations, build servers, and CI agents rather than general end-user endpoints. The issue scores 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) with total technical impact, no public exploit has been identified at time of analysis, and vendor-released patches are available. This is a credible but not emergency-grade issue, best treated as routine-high patching priority rather than a drop-everything event.
Remote code execution in Microsoft .NET allows an unauthenticated attacker to execute arbitrary code when a legitimate user opens or loads crafted content that triggers an out-of-bounds write in the runtime. The flaw affects a broad range of .NET Framework versions (3.5 through 4.8.1), modern .NET 8.0, 9.0, 10.0, and 11.0 preview, plus Visual Studio 2022 and 2026. No public exploit code or active exploitation has been identified at time of analysis, and CISA SSVC rates the issue as non-automatable, though the mandatory user interaction and wide deployment make patching critical for unpatched systems.
Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) component of .NET, specifically runtimes 8.0.0 through 8.0.31, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, as well as Visual Studio 2022 17.14 and Visual Studio 2026 18.10 installations that carry the vulnerable runtime. An unauthenticated attacker can deliver crafted content that, when a victim interacts with an XPS document whose synthetic hyperlinks are exposed through UI Automation, bypasses the application's restrictive navigation checks and reaches attacker-controlled content, leading to code execution in the context of the running application; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms high confidentiality, integrity, and availability impact but explicitly requires user interaction. Vendor patches are available (runtime fixes 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2), and no public exploit code was identified at time of analysis despite the network-reachable attack path.
Unauthenticated remote attackers can drive CPU exhaustion in .NET applications that validate untrusted signed CMS/PKCS#7 data, because SignedCms.CheckSignature in the System.Security.Cryptography.Pkcs package repeatedly reparses attacker-controlled X.509 content at quadratic cost (CWE-407, CVSS 7.5, AV:N/AC:L/PR:N/UI:N with availability-only impact, C:N/I:N/A:H). Affected build ranges are System.Security.Cryptography.Pkcs 8.0.0 through 8.0.1, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, along with the listed .NET Framework 3.5 / 4.6.2 / 4.7 / 4.7.1 / 4.7.2 / 4.8 / 4.8.1 servicing baselines and Visual Studio 2022 17.14 and Visual Studio 2026 18.10. Exploitation is bounded to services that actually accept and cryptographically verify externally supplied signed CMS messages through this API; no public exploit identified at time of analysis, and CISA SSVC records exploitation as none.
Remote code execution in .NET WPF (Microsoft.WindowsDesktop.App.Runtime) allows an unauthenticated attacker to execute code on a victim's Windows system by crafting a malicious XAML/XPS document or serialized payload and convincing the user to open or load it. The vulnerability is a CWE-502 deserialization of untrusted data issue rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); exploitation requires user interaction and is not automatable (SSVC Automatable=no, Exploitation=none). No public exploit code or active exploitation has been identified at time of analysis, though vendor patches are available for all affected .NET and .NET Framework versions.
Memory corruption in Microsoft .NET's System.Net.Sockets component allows an unauthorized attacker to execute code over a network on Windows hosts, but only against applications that reuse a single SocketAsyncEventArgs instance across both IPv4 and IPv6 UDP datagram sockets. The flaw (CVSS 8.1, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) manifests as an out-of-bounds write in the ReceiveFromAsync path once an undersized cached native address buffer is retained; no authentication or user interaction is required, though the high attack complexity reflects the non-default coding pattern required to reach the vulnerable state. There is no public exploit identified at time of analysis, CISA SSVC records exploitation as none and non-automatable, and no KEV listing applies; Microsoft has shipped fixed runtime builds, making this a meaningful but non-emergency patching priority.
Path traversal in .NET (CWE-22) allows an authenticated local attacker to escape an intended restricted directory and elevate privileges on the host, with the same flaw reaching users through the Visual Studio 2022 17.14 and Visual Studio 2026 18.10 toolchains. Successful exploitation requires a local, already-authenticated foothold (PR:L) plus user interaction (UI:R), meaning a higher-privileged user or process must be induced to act on an attacker-influenced pathname; it is therefore not remotely triggerable, and CISA's SSVC assessment records Exploitation: none, Automatable: no, with total technical impact if it does succeed. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this rates as a moderate-priority local privilege-escalation issue rather than an urgent, widely exploitable threat. Vendor patches are available.
Denial of service in Microsoft .NET lets an unauthenticated remote attacker force the runtime into disproportionately expensive computation, driving CPU or memory consumption high enough to degrade or halt a service. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) confirms remote, low-complexity, unauthenticated exploitation with no user interaction and a high availability-only impact, requiring only that the vulnerable .NET code path be reachable by attacker-supplied network input - no public exploit code was identified at time of analysis and the issue is not listed in CISA KEV. Exposure is limited to reachable, .NET-based services; internal-only or non-.NET-facing deployments are not affected, and the exact affected runtime versions must be confirmed against the MSRC advisory.
Type confusion (CWE-843) in Microsoft .NET and Visual Studio allows an unauthenticated remote attacker to elevate privileges when a victim opens, loads, or builds attacker-supplied content in developer tooling, rated CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is not zero-click: an attacker must socially engineer a developer into processing a malicious file, project, or package so the type-confusion code path is reached, and the practical limiting factor remains that user-interaction requirement. No CISA KEV entry, no public exploit code, and no EPSS data were provided at time of analysis, so this is a credible high-priority issue but with important caveats.
Hard-coded JWT signing key in BotSharp through 5.2.0 allows unauthenticated remote attackers to forge bearer tokens and impersonate any user, including administrators, on Authorize-protected API routes. Exploitation requires the deployment to retain the default key and default 'botsharp' issuer/audience; rotating these values mitigates the issue. No public exploit code has been identified at the time of analysis, but the high impact and low complexity make this a genuine high-priority risk as confirmed by independent assessment.
Memory corruption in SixLabors ImageSharp 4.0.0 through 4.1.1 allows an unauthenticated remote attacker to crash or destabilize a host process by supplying an image whose embedded ICC profile declares more than four LUT16 input/output channels, causing out-of-bounds writes past a four-float internal buffer. The flaw is only reachable when an application has explicitly set DecoderOptions.ColorProfileHandling to Convert, since the default Preserve mode does not run ICC conversion; the independent assessment scores it CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), reflecting an availability-only impact rather than data disclosure or modification. No public exploit code was identified at time of analysis, and the issue is fixed in version 4.1.2.
PKIX certificate path validation in the Bouncy Castle C# library (bc-csharp) before 2.7.0 accepts certificates whose subject distinguished name, or directoryName subjectAltName, falls outside a name-constrained intermediate CA's permitted subtrees, breaking the RFC 5280 name-constraint trust boundary. An unauthenticated attacker who controls, or can obtain certificates from, a name-constrained intermediate CA already present in a chain the victim validates can craft a DN that prepends extra RDNs ahead of a copy of the permitted RDN sequence and have it accepted by PkixNameConstraintValidator.WithinDNSubtree. Vendor-released patches are available in the 2.7.0 codebase (commits 606e9153b97a265c70ca8293d21ec859344d7de8 and 75c3c576602886180ed92a63c89419e3bd63b392), and no public exploit code has been identified at time of analysis; exploitation is gated by the precondition that a name-constrained CA must already be positioned in the validated chain, so environments that do not enforce directoryName name constraints are unaffected.
Denial of service in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows unauthenticated remote attackers to exhaust process memory by supplying crafted OpenPGP public keys, certificates, or signatures, because a subpacket header using the five-octet (0xFF) length form declares an oversized body length that is used directly to size a buffer before any subpacket data is read. The flaw lives in SignatureSubpacketsParser.ReadPacket and UserAttributeSubpacketsParser.ReadPacket (CWE-789, memory allocation with excessive size value) and is rated CVSS 4.0 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VA:H) and an independently assessed CVSS 3.1 of A:H with no confidentiality or integrity impact; a handful of input bytes can demand an allocation of up to roughly 2 GB (the 32-bit length field permits up to ~4 GB in principle), so any service that imports or verifies untrusted PGP material is exposed. Vendor patches are available (bc-csharp 2.7.0) and no public exploit code has been identified at time of analysis, though the upstream regression test does illustrate the malicious packet format.
Crafted small-order or out-of-range Diffie-Hellman values passed to DHAgreement.CalculateAgreement in Bouncy Castle C# (bc-csharp) before 2.7.0 let an on-path attacker or malicious peer defeat the key authentication MTI/A0 is designed to provide and, when the local party reuses a static DH private key, learn that key modulo the small factors of p-1 - with full recovery possible in groups where p-1 has many small prime factors. The issue is unauthenticated (CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N), and exploitation is not opportunistic: it works only where an application calls DHAgreement directly in an MTI/A0 two-pass flow, and it requires a protocol peer or on-path attacker able to inject a crafted 'message' or public-key value; higher-level Bouncy Castle protocol wrappers are unaffected. No public exploit code or confirmed active exploitation was identified at time of analysis, and the independent assessment rates real-world blast radius as narrower than the 9.1 CVSS 4.0 base score suggests because of the narrow direct-caller API surface, the static-key reuse prerequisite, and the dependence on weak group parameters for complete key recovery.
On-path attackers who can intercept and modify CMS messages can silently tamper with AES-CCM-protected content that Legion of the Bouncy Castle Inc.'s bc-csharp library (versions before 2.7.0) decrypts. The root cause is that CcmParameters accepted any aes-ICVlen value from an untrusted AlgorithmIdentifier while CcmBlockCipher enforced the tag length only on the encryption path, so a decryption carrying a zero-length or very short tag compared an empty or truncated tag and accepted forged ciphertext without any detectable integrity failure; the same fix also hardens the AES-GCM CMS parameter handling. The reachable paths are ParameterUtilities.GetCipherParameters as used by CmsEnvelopedData and CmsEnvelopedDataParser for AES-CCM EnvelopedData, plus any caller that forwards an unchecked tag length into CcmBlockCipher for decryption. A vendor patch is available in 2.7.0 and the change is published as two commits plus a wiki advisory; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and because exploitation requires an attacker to already hold a network interception position (no remote-from-anywhere access, no authentication, no user interaction), the practical risk is a genuine but precondition-gated integrity/tampering issue rather than a broadly exploitable one.
Progress Software Fiddler Everywhere 8.0.2 ships a local .NET backend (Fiddler.WebUi) that exposes an HTTP and SignalR RPC endpoint on the loopback interface without any authentication, allowing any local user or process on the same machine to call privileged methods, mint OAuth tokens, and export the application's machine-in-the-middle root certificate. The issue is strictly local (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, 7.7) and only exploitable while Fiddler Everywhere is installed and running, but it requires no credentials or user interaction once those conditions hold. There is no evidence of active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; the practical risk is credential and trust-anchor theft on shared workstations or hosts where untrusted local software can execute.
Argument injection in the CliInvoke .NET process-wrapping library (and its former identity, AlastairLundy.CliInvoke) allows a double quote in a caller-supplied target or argument to break out of the operating-system-level quoted region and add unintended elements to a runner's argument vector, potentially escalating to arbitrary command execution when a shell runner is used. Affected versions span CliInvoke 2.0.0-2.8.4, 2.9.0-2.9.3, 2.10.0-2.10.4 and 3.0.0-alpha.1-3.0.0-beta.1, plus AlastairLundy.CliInvoke 2.0.0-alpha.1-2.0.0; the flaw is reachable only when a consuming .NET application routes attacker-influenced data through RunnerProcessFactory (2.x) or RunnerConfigurationFactory (3.x) instead of building a ProcessConfiguration with an explicit ArgumentList. Scored CVSS 3.1 8.4 (High) with vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, it carries no public exploit identified at time of analysis and is not in CISA KEV.
Malformed service-registry records can blank out service discovery for Steeltoe-based cloud-native applications: EurekaDiscoveryClient versions 4.0.0 through 4.2.x deserialize the entire Eureka registry response as one atomic unit, so a single instance entry with an unrecognized actionType or status, a non-Boolean isCoordinatingDiscoveryServer, or a nonnumeric timestamp aborts the whole payload and leaves every connected client with an empty or stale instance list. The vendor rates this 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) while the independent assessment rates the vector with PR:L and scope changed, reflecting that a practical attacker must be a principal able to register or update an instance in the Eureka registry that victim clients consume; impact is availability-only, with no data exposure or code execution, and the effect self-heals once the bad registration is removed. No public exploit code has been identified at time of analysis and the issue is fixed in Steeltoe 4.3.0.
Consul service discovery in Steeltoe 4.0.0 through 4.2.x can be rendered persistently unusable by a single malformed service registration, because ConsulServiceInstance parses the registration's 'secure' metadata with a strict Boolean conversion that throws on any value other than 'true' or 'false'. A principal able to write to the Consul catalog - i.e. holding a valid ACL token with service-registration rights, or reaching a Consul deployment that runs without ACLs - can register a service whose 'secure' metadata is set to a value such as 'yes', '1' or an empty string; the resulting exception aborts construction of the instance list, and because GetAllInstancesAsync throws on the first bad entry, enumeration of every discovered service fails, taking the target (or the entire discovery surface) offline until the offending registration is removed. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (the advisory's vector differs only in reporting PR:N instead of PR:L), and while no public exploit code has been identified at time of analysis, no CISA KEV entry exists, and no EPSS score was supplied, the impact is low-complexity and requires no user interaction, so Consul catalog write access should be treated as a denial-of-service primitive.
SQL injection (CWE-89) in Marten, the .NET transactional document DB and event store for PostgreSQL, affects versions 7.0.0 through 9.12.x and lets an authenticated attacker who can influence strings reaching Marten's LINQ or tenant-management paths break out of single-quoted SQL/JSON-path literals and inject an always-true predicate, causing filter or multi-tenant authorization bypass and blind data exfiltration; on deployments that permit semicolon-batched Npgsql statements, data modification is also possible. The primary confirmed vector is a dictionary indexer key used in Where filters (src/Marten/Linq/Members/Dictionaries/DictionaryItemMember.cs); Dictionary.ContainsKey is exploitable only under the Newtonsoft serializer, tenant identifiers reaching DeleteAllForTenant.cs via IEventStore.DeleteProjectionProgressAsync are likewise affected, and EventLoader.cs contains a related defense-in-depth sink. The vendor confirmed the issue in GHSA-rfx3-98h7-v3xp and fixed it in version 9.13.0 via PR #4911; no public exploit code was identified at time of analysis, and exploitation requires the host application to route attacker-controlled strings into one of these Marten paths.
XML external entity (XXE) injection in the IBM MQ .NET client allows an authenticated attacker with queue-write access to read files from the host running that client and to cause a limited denial of service when the client parses the RFH2 folder of a crafted message. The flaw is client-side - the queue manager itself and the Java/C clients are not indicated as affected - and the attacker must already hold valid MQ credentials with authority to place messages on a queue the vulnerable client consumes. No public exploit has been identified at time of analysis, CISA's SSVC assessment records no exploitation activity and rates the issue not automatable with partial technical impact, and patch code is available from the vendor; the practical risk is genuine but moderate, well below what the 7.1 base score suggests at first glance.
Privilege elevation in Microsoft Visual Studio 2022 (17.14.0 to <17.14.40), Visual Studio 2026 (18.9.0 to <18.9.3), and the Microsoft.Diagnostics.Runtime (ClrMD) library stems from external control of a file name or path (CWE-73) that a higher-privileged process then resolves without canonicalization, letting an unauthenticated remote attacker influence which file is opened or executed and thereby gain the privileges of the resolving process. The assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CVSS 8.1) confirms no authentication or user interaction is required, but the high attack-complexity rating reflects that success depends on specific input conditions and on whether the affected developer/diagnostics component actually consumes attacker-influenced paths in a given deployment. Risk signals are mixed: EPSS is only 0.51% (42nd percentile), CISA SSVC records Exploitation: none and Automatable: no, and no public exploit code has been identified at time of analysis, so this is a high-severity but not high-urgency issue; vendor patches are available and the affected components are developer tooling rather than always-on network services.
The OpenTelemetry .NET OTLP exporter's experimental disk-retry feature can be abused by an authenticated local attacker when `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk` is set without `OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH`, causing retry blobs to be written to and read from fixed `traces`, `metrics` and `logs` subdirectories under the shared system temp root. An attacker holding a separate local account with read/write access to that temp directory can inject crafted `*.blob` files that the exporter later forwards to the configured OTLP endpoint under the application's identity and credentials, read the application's own serialized telemetry blobs, or flood the retry loop with oversized files to degrade performance and consume disk. The affected NuGet package is `OpenTelemetry.Exporter.OpenTelemetryProtocol` from 1.8.0 through 1.15.2 and is fixed in 1.15.3; the feature is experimental and off by default, exposure only arises when the directory variable is omitted, and no public exploit code was identified at time of analysis (EPSS 0.01%, no KEV entry), so risk is real but conditional on shared-temp multi-user hosts.
Insecure .NET Remoting deserialization in Altec DocLink (Beyond Limits) 4.0.336.0. Exposed TCP endpoints allow unauthenticated remote code execution via .NET Remoting deserialization attacks.
Configuration injection in OpenClaw Docker sandbox before 2026.2.15 allows escaping sandbox restrictions. Patch available.
Static ASP.NET machineKey in Calero VeraSMART before 2022 R1. Hardcoded key enables ViewState deserialization attacks and cookie forgery.
Unauthenticated .NET Remoting endpoint in Calero VeraSMART before 2022 R1. TCP port 8001 exposes default Object URIs enabling deserialization attacks. EPSS 0.17%.
.NET applications are vulnerable to spoofing attacks due to improper validation of a required security element, allowing unauthenticated remote attackers to forge or manipulate application data over the network. This vulnerability affects multiple .NET versions and currently has no available patch, exposing organizations to authentication bypass and data integrity risks. The attack requires no user interaction and can be exploited directly from the network.
PowerDocu versions prior to 2.4.0 allow arbitrary .NET object instantiation and code execution through unsafe deserialization of the $type property in JSON files within Flow or App packages. A local attacker with user interaction can exploit this vulnerability to achieve full system compromise. Public exploit code exists for this vulnerability, and no patch is currently available for affected versions.
Microsoft Semantic Kernel SDK has a CVSS 9.9 path traversal vulnerability enabling AI agents to access arbitrary files outside their intended scope.
DNN (DotNetNuke) CMS has a stored XSS vulnerability (CVSS 9.1) allowing persistent script injection that executes for all users viewing the affected content.
Stored cross-site scripting in DNN versions 9.0.0 through 9.13.9 and 10.0.0 through 10.1.x allows high-privileged users with UI interaction to inject malicious scripts into module friendly names that execute within the Persona Bar administrative interface. An authenticated attacker with sufficient permissions could exploit this to perform administrative actions or compromise other users' sessions. No patch is currently available for affected versions.
Stored cross-site scripting in DNN versions 9.0.0 through 9.13.9 and 10.0.0 through 10.1.x allows authenticated administrators with high privileges to inject malicious scripts into log notes that execute within the PersonaBar interface. An attacker with admin credentials could perform actions as the victim or steal session data when the logs are viewed. Upgrade to DNN 9.13.10 or 10.2.0 to remediate this vulnerability.
DotNetNuke versions prior to 9.13.10 and 10.2.0 allow arbitrary script execution in the Persona Bar administrative interface through unsanitized richtext content in module descriptions. An authenticated attacker with module installation privileges can inject malicious scripts that execute in the context of administrative users, potentially compromising sensitive data or administrative functions. This vulnerability requires high privileges and user interaction to exploit, with no public patch currently available for affected versions.
Client-side field-level encryption (CSFLE) in the MongoDB .NET/C# driver silently writes fields that should have been encrypted as plaintext when the process runs under certain platform text-encoding configurations, because an internal name conversion loses information and the operation is never matched to its configured encryption rules. Affected are driver versions from 2.10.0 up to but not including 3.13.0, and only deployments that actually have CSFLE configured and in use; an application user able to write data through such an application can cause sensitive fields to be persisted unencrypted with no error raised. There is no integrity or availability impact, no public exploit identified at time of analysis, and the issue is resolved in driver release 3.13.0.
Improper authentication in the dotnet eShop Catalog API's AddApplicationServices configuration lets unauthenticated remote attackers bypass authentication controls and achieve limited confidentiality, integrity, and availability impact on catalog data; affected builds are up to commit 913acea66708a59595351174cee9b29f37179d29. The CVSS v4 vector records Proof-of-Concept exploit maturity (E:P), so publicly available exploit code exists, but there is no confirmed active exploitation (not in CISA KEV). Because eShop is a Microsoft reference/sample application rarely exposed in production, practical risk is moderate and bounded to low-impact catalog-level effects.
Oqtane Framework through 10.2.6 exposes one tenant's stored private settings to the administrator of another tenant, allowing an authenticated site administrator to retrieve SMTPPassword and SMTPClientSecret values by requesting a foreign site's entityId through their own site alias. The flaw is an authorization bypass in SettingController (CWE-639, user-controlled key), scored 6.9 Medium under CVSS 4.0 (AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N) and assessed as CVSS 3.1 6.0-style confidentiality-only impact (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N). Exploitation requires a multi-tenant Oqtane deployment hosting more than one site plus the attacker already holding the Administrators role on at least one tenant site; single-site installations are unaffected, no public exploit identified at time of analysis, and the impact is limited to credential disclosure with no integrity, availability, or code-execution effect (vendor advisory: https://www.vulncheck.com/advisories/oqtane-framework-through-10.2.6-cross-site-settings-disclosure-via-setting-api).
Denial of service in MessagePack-CSharp occurs when an application deserializes attacker-controlled MessagePack data into System.Object through PrimitiveObjectFormatter: the formatter allocates an object[] sized from each declared array length before the configured object-graph depth limit is applied, and nested array headers can reuse the same trailing unread bytes to satisfy per-header length validation, so a small payload (reported ~31.5 KiB) can hold roughly 114.7 MiB of reference storage live at once and, with repeated submissions, cause severe managed-heap pressure, excessive garbage collection, process termination, or loss of service. Affected releases are all MessagePack-CSharp versions before 2.5.303 and 3.x versions from 3.0.0 up to but excluding 3.1.9 (2.5.302 is confirmed vulnerable), with the named concrete exposure being an ASP.NET Core SignalR application that has AddMessagePackProtocol() enabled and a reachable hub method taking an object parameter. The CVSS vector is AV:N/AC:L/PR:N/UI:N with availability-only impact (C:N/I:N/A:L), so publicly reachable endpoints need no credentials while protected endpoints keep their existing authorization; exploitation requires repeated attacker-controlled submissions rather than a single request, and no public exploit code was identified at time of analysis.
Authenticated attackers with read and metadata-write access to encrypted objects in Amazon S3 can force a padding downgrade in the Amazon.Extensions.S3.Encryption .NET client, then use a Bleichenbacher padding oracle to recover the RSA-wrapped envelope key and decrypt the object. Affected versions are before 3.2.2 and 4.0.x before 4.0.3; the 1.x and 2.x lines are unpatched and must be migrated. Exploitation requires valid credentials, metadata modification permissions, and many decryption queries, so no public exploit identified at time of analysis, consistent with SSVC Exploitation: none.
Origin-validation bypass in Microsoft .NET 8.0, 9.0, 10.0 and 11.0 (plus bundled Visual Studio 2022 17.14 and Visual Studio 2026 18.10 builds) lets an unauthenticated remote attacker defeat a built-in security feature when a victim interacts with attacker-supplied cross-origin content, producing integrity-only impact (CVSS 6.5, I:H with no confidentiality or availability loss). The mandatory user-interaction step (UI:R) and the fact that exploitation depends on the application actually relying on the affected origin-checking feature keep this at moderate severity; there is currently no public exploit identified at time of analysis, CISA SSVC records exploitation as none and automation as no, and EPSS/KEV data is absent. Vendor patches are available (MSRC advisory msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96238).
Information disclosure in the Windows Desktop Runtime (WPF) component of .NET allows a remote, unauthenticated attacker to read data from a victim's machine when the victim opens or navigates a crafted XAML or XPS document - or content that causes WPF to fetch a remote URI or TrueType font - inside a WPF-based desktop application on Windows. Per the independent assessment, exploitation is constrained by mandatory user interaction (UI:R) and high attack complexity (AC:H) tied to specific conditions in the XAML/XPS parsing and hyperlink-navigation path, and no public exploit code or confirmed active exploitation has been identified at time of analysis, keeping real-world priority low-to-moderate despite the CVSS 5.3 moderate rating and high confidentiality impact. Affected builds span .NET 8.0, 9.0, 10.0 and 11.0 previews as well as Visual Studio 2022 17.14 and Visual Studio 2026 18.10, which ship the vulnerable runtime.
Use-after-free in the Microsoft QUIC (MsQuic) Schannel native library allows an unauthenticated, remote attacker who can reach a QUIC/HTTP-3 endpoint to disclose memory contents over the network, with impact limited to confidentiality (no integrity or availability effect). Affected software includes .NET applications referencing the Microsoft.Native.Quic.MsQuic.Schannel package in versions 1.9.0 through 2.6.1, plus a broad set of Windows 11 and Windows Server 2022/2025 builds and Visual Studio 2022/2026 that ship the vulnerable QUIC binaries. Exploitation is non-deterministic because the CVSS vector (AC:H) reflects a race condition the attacker must win, and no public exploit code has been identified at time of analysis; the CISA SSVC assessment records exploitation as none and the issue as not automatable, making this a genuine-but-moderate risk rather than a fire-drill.
Improper certificate validation in .NET 11's System.Net.Security component allows a remote, unauthenticated attacker to bypass mutual TLS authentication, because post-handshake TLS client authentication can fail to verify the client certificate. Only pre-release .NET 11 builds (11.0.0-preview.1 through 11.0.0-rc.1) running on Linux or macOS are affected, and exposure requires the application to use post-handshake mTLS client-certificate authentication with a server that is configured to require client certificates. No public exploit code has been identified at time of analysis, and remediation is available in .NET 11.0.0-rc.2, Visual Studio 2026 18.10.4, and Visual Studio 2022 17.14.42.
A pre-authentication denial-of-service condition in the .NET cryptographic library System.Security.Cryptography.Pkcs causes CPU exhaustion on Windows when `EnvelopedCms.Decode` processes specially crafted CMS/PKCS#7 attribute sets, because the decoding routine performs quadratic work proportional to the number of attacker-supplied attributes rather than linear work. Affected applications are Windows-hosted .NET apps that reference a vulnerable package version (8.0.0-8.0.1, 9.0.0-9.0.20, 10.0.0-10.0.12, or 11.0.0-preview.1 through 11.0.0-rc.1) and pass untrusted PKCS#7/CMS enveloped data into the decode path - a pattern common in S/MIME mail gateways, signed-message web endpoints, and certificate/token processing services; there is no impact to confidentiality or integrity (CVSS 5.9, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-405). Exploitation requires no authentication or user interaction but is constrained by the Windows-only scope, the requirement that the vulnerable CMS decode path actually be reachable from untrusted input, and high attack complexity (AC:H) needed to tune payloads for meaningful amplification; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', and no public exploit identified at time of analysis, though vendor-released patches are available. Visual Studio 2022 (17.14.0-17.14.41) and Visual Studio 2026 (18.10.0-18.10.3) installations that bundle the affected SDK/runtime are also in scope.
Information disclosure in .NET's System.Net.Http affects applications that use SocketsHttpHandler with an authenticating proxy, because the Proxy-Authorization header is retained when an outbound request is redirected and is then sent to the redirect destination, exposing Basic proxy credentials to a server the attacker can observe or control. Affected runtimes are .NET 8.0 before 8.0.32, 9.0 before 9.0.21, 10.0 before 10.0.13 and 11.0 before 11.0.0-rc.2, with Visual Studio 2022 17.14 before 17.14.42 and Visual Studio 2026 18.10 before 18.10.4 shipping the same component; the CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (5.9), reflecting high attack complexity rather than any authentication requirement. There is no public exploit identified at time of analysis - CISA's SSVC assessment rates exploitation as none and automatable as no - but the severity comes from a leaked credential, not from any integrity or availability impact, and the exposure is limited to the proxy secret rather than general application data.
Log-integrity tampering in the RemoteSyslogAppender of Apache log4net affects versions from 1.2.12 up to but not including 3.5.0, where characters outside the visible ASCII range are silently deleted from syslog records instead of being escaped. An unauthenticated remote party who can influence a value that reaches a log message (for example, a username containing a zero-width space) can make a distinct value appear identical to another in the audit record, such as a user name being logged as 'admin'. Only applications that explicitly configure RemoteSyslogAppender are affected; deployments using file, console, or other appenders are not. Impact is limited to integrity of the log record (CVSS I:L) with no confidentiality or availability effect, and no public exploit has been identified at time of analysis.
Improper handling of Unicode encoding in Apache log4net's SmtpPickupDirAppender lets an attacker who can place unencodable content - such as an unpaired UTF-16 surrogate like U+D800 - into a logged message break the appender's file writer, causing the entire buffered batch of logging events to be discarded rather than just the offending event, and leaving a truncated mail file in the pickup directory for the mail service to send. Only applications configured to use SmtpPickupDirAppender (the SMTP pickup-directory appender) with event buffering are affected; versions from 1.2.9 before 3.5.0 are impacted. The issue is rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) - remote and unauthenticated once attacker data reaches a rendered log field - but impact is confined to integrity of log output (suppression/truncation of audit records), with no confidentiality or availability loss; no public exploit code was identified at time of analysis and it is not confirmed actively exploited (not in CISA KEV).
Field level encryption can be silently disabled in applications built on the MongoDB Entity Framework Core Provider when the connection string places a database name there, causing sensitive fields to be stored or read without the intended protection. This affects only applications that rely on field level encryption to protect sensitive data; deployments not using FLE are unaffected. The attacker must already have read access to the MongoDB datastore, backups, or network traffic to benefit, and no public exploit identified at time of analysis. The CVE feed lists CVSS 6.8, while the independent assessment rates it as a conditional data-protection weakness (CWE-311), not a remote code-execution flaw.
Sensitive credential disclosure in the MongoDB Entity Framework Core Provider occurs when the application runs with DEBUG-level logging enabled or when a malformed MongoDB connection string is supplied, causing the provider to record the connection string - including any embedded passwords and AWS secret access keys, where used - into application logs. Realistic exploitation requires local access plus existing privileges sufficient to read those logs, and it is confined to non-default configurations; deployments that obtain credentials from IAM roles or secret managers rather than inline connection strings are largely unaffected. No public exploit has been identified at time of analysis, and this is a genuine but low-to-moderate priority information-disclosure flaw rather than an urgent one.
MongoDB EF Core silently drops TLS and schema-map (client-side field-level/queryable encryption field map) settings when an application configures encryption both through independent/application-level settings and through the provider's own encryption settings, causing fields that were meant to be encrypted to be persisted in the database as cleartext. Only .NET applications built on the MongoDB Entity Framework Core Provider that combine both encryption configuration paths are affected; deployments using a single path, or not using field encryption at all, are not affected. No public exploit identified at time of analysis - the flaw is a silent misconfiguration with no attacker interaction at write time, and actual disclosure additionally requires a party to gain read access to the underlying MongoDB data, backups, or logs (CWE-311, Missing Encryption of Sensitive Data).
Authentication bypass in Steeltoe.Security.Authorization.Certificate (Steeltoe prior to 4.3.0) lets remote unauthenticated attackers spoof the X-Client-Cert header to defeat the SameOrg and SameSpace authorization policies, gaining access to resources belonging to another organization or space. The flaw is that AddOrgAndSpacePolicies() combined with UseCertificateAuthorization() trusts a client-supplied public certificate without verifying proof of possession of the matching private key, and common Cloud Foundry routers pass the header through to the application. Exploitation is unauthenticated (PR:N) but high complexity (AC:H) and only succeeds when ingress does not restrict inbound traffic to a known trusted proxy source IP and the attacker already holds the public certificate of an application instance in the target org or space; there is no public exploit code and no CISA KEV entry, and EPSS data was not provided, so the practical risk is moderate and deployment-dependent. Fixed in Steeltoe 4.3.0.
Information disclosure in Steeltoe's Management Endpoint actuator (Steeltoe.Management.Endpoint) prior to 4.3.0 allows an unauthenticated remote attacker who can reach the exposed /actuator/httpexchanges endpoint to harvest secrets that were previously captured in recorded request query strings - OAuth and password-reset tokens, API keys, and signed-URL signatures - because MaskedUri only redacts URI user-info and never inspects the query string. The same recorded URIs are written by the Steeltoe.Management.Endpoint.Actuators.HttpExchanges DEBUG logger, giving anyone with log access a second disclosure channel. Exploitation is config-gated (IncludeQueryString must be enabled, the endpoint must be explicitly exposed, and prior traffic must actually have carried query-string secrets), scoring CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/C:H/I:N/A:N); no public exploit identified at time of analysis, and the issue is remediated in Steeltoe 4.3.0.
Asp.Net-Core-Inventory-Order-Management-System versions up to 9.20250118. contains a security vulnerability (CVSS 6.3).
NanaZip versions 5.0.1252.0 through 6.5.1637.x contain an integer underflow in the .NET Single File Application parser that allows local attackers with user privileges to cause denial of service through unbounded memory allocation when opening a specially crafted archive file. Public exploit code exists for this vulnerability. Patches are available in versions 6.0.1638.0 and 6.5.1638.0.
Out-of-bounds memory read in NanaZip versions 5.0.1252.0 through 6.0.1637.x allows local authenticated attackers to disclose in-process memory or trigger application crashes by crafting malicious .NET Single File Application bundles with malformed manifest headers. Public exploit code exists for this vulnerability, and patches are available in versions 6.0.1638.0 and 6.5.1638.0. The issue affects Dotnet and Nanazip products where a malicious user interaction with crafted archive files can bypass bounds checking during manifest parsing.
The Print Service component of Fiserv Originate Loans Peripherals (formerly Velocity Services) in unsupported version 2021.2.4 (build 4.7.3155.0011) uses deprecated .NET Remoting TCP channels that allow unsafe deserialization of untrusted data.
NanaZip versions 5.0.1252.0 through 6.0.1629.0 contain an out-of-bounds heap read in the .NET Single File bundle parser that can crash the application or expose sensitive heap memory when processing malicious archive files. A local attacker with user privileges can exploit this vulnerability by crafting a specially formatted file, and public exploit code is currently available. No patch is yet available for affected users.
SD.NET RIM versions before 4.7.3c contain a SQL injection vulnerability that allows attackers to inject malicious SQL statements through POST parameters 'idtyp' and 'idgremium'. [CVSS 8.2 HIGH]
Htmlsanitizer versions up to 9.0.892 is affected by improper encoding or escaping of output (CVSS 6.1).
DotNetNuke 9.5 contains a persistent cross-site scripting vulnerability that allows normal users to upload malicious XML files with executable scripts through journal tools. [CVSS 6.4 MEDIUM]
Stored cross-site scripting in DNN versions 9.0.0 through 10.1.x allows content editors to inject malicious scripts into module headers and footers that execute in the browsers of other users. An authenticated editor with content creation privileges can exploit this to steal session tokens, perform actions on behalf of other users, or redirect them to malicious sites. Updates to version 9.13.10 or 10.2.0 are required to remediate the vulnerability.
Exos 9300 instances are using a randomly generated database password to connect to the configured MSSQL server. The password is derived from static random values, which are concatenated to the hostname and a random string that can be read by every user from the registry.
The PeachPay - Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net) plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability checks on the ConvesioPay webhook REST endpoint in all versions up to, and including, 1.119.8. [CVSS 5.3 MEDIUM]
Changjetong T+ (through 16.x) has .NET deserialization RCE in an AjaxPro endpoint. Attacker-controlled JSON triggers deserialization of malicious .NET types. PoC available.
Entrust Instant Financial Issuance (IFI) On Premise software (formerly referred to as CardWizard) versions 5.x, prior to 6.10.5, and prior to 6.11.1 contain an insecure .NET Remoting exposure in the SmartCardController service (DCG.SmartCardControllerService.exe).
AWS SDK for .NET works with Amazon Web Services to help build scalable solutions with Amazon S3, Amazon DynamoDB, Amazon Glacier, and more. From versions 4.0.0 to before 4.0.3.3, Customer applications could be configured to improperly route AWS API calls to non-existent or non-AWS hosts. This notification is related to the use of specific values for the region input field when calling AWS services. An actor with access to the environment in which the SDK is used could set the region input fie...
Remote code execution in the ActiveMQ NMS AMQP .NET client affects all releases up to and including 2.3.0 when the client initiates an AMQP session to an attacker-controlled, compromised, or otherwise untrusted broker; that server can return crafted serialized data the client deserializes without bounds, potentially executing arbitrary code on the client host. The primary prerequisite is control or impersonation of the broker endpoint the client connects to, so deployments that only talk to trusted, internally controlled brokers are not realistically exploitable without first compromising that broker or the network path, and the allow/deny-list deserialization restriction added in 2.1.0 is bypassable so enabling it does not guarantee protection. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); EPSS is 2.09% (81st percentile) and the vendor-released fix is version 2.4.0.
Unauthenticated remote attackers can connect to a TLS-enabled Akka.Remote cluster without presenting a client certificate and fully participate in cluster communication, because Akka.Remote never requested the connecting peer's certificate in versions 1.2.0 through 1.5.51 - mutual TLS was simply not implemented. Any deployment that enabled TLS via the akka.remote.dot-netty.tcp transport to secure remoting and is reachable by untrusted parties is affected, yielding high confidentiality and integrity impact (CVSS 3.1 9.3 from the vendor; independent assessment scores AV:N/AC:L/PR:N/UI:N with C:H/I:H/A:N). There is no public exploit code identified at time of analysis and EPSS is low (0.31%, ~22nd percentile), but impact is deployment-conditional: clusters confined to a fully trusted private network, or that never enabled TLS, see no practical risk. Untrusted parties on the network path can obtain a position to join the cluster and exchange messages.
CVE-2025-30399 is an untrusted search path vulnerability in .NET and Visual Studio that allows unauthenticated remote attackers to execute arbitrary code through a network vector, requiring user interaction. The vulnerability affects multiple versions of .NET Framework and Visual Studio across Windows platforms. While the CVSS score is 7.5 (high), the attack complexity is high and requires user interaction, potentially limiting real-world exploitation frequency.
Critical authentication bypass vulnerability in ArchiverSpaApi ASP.NET applications caused by hard-coded JWT signing keys. An unauthenticated remote attacker can forge valid JWT tokens to bypass authentication and gain unauthorized access to protected API endpoints, potentially leading to data exfiltration, modification, or denial of service. The CVSS 8.1 score reflects high confidentiality, integrity, and availability impact, though the attack complexity is rated as high, suggesting some technical prerequisites.
Weak authentication in ASP.NET Core & Visual Studio allows an unauthorized attacker to elevate privileges over a network. [CVSS 7.0 HIGH]