Ocaml
Monthly
Denial of service in Robur Albatross (specifically the albatross-console component) versions 1.0.0 through 2.x before 2.7.2 lets an authenticated user who can send console subscription commands drive the albatross-console process into an unterminated loop over the unikernel log ring buffer, consuming CPU and making console access unavailable. Exploitation requires the targeted unikernel to have generated enough output to fill the 1024-line ring buffer, and the request must specify a very high or negative line count, or a timestamp earlier than every buffered message; the vendor states it is not exploitable by unauthorized clients, and the independent assessment confirms PR:L with availability-only impact (C:N/I:N/A:H). No public exploit code has been identified at time of analysis, so this is a genuine but bounded availability risk rather than a high-urgency threat.
Index mishandling in the OCaml cstruct library before 6.3.0 allows network-reachable attackers to trigger partial confidentiality, integrity, and availability impacts via crafted binary data passed to affected parsing routines. cstruct is a low-level binary buffer manipulation library used widely in OCaml network stacks and the MirageOS unikernel ecosystem; improper index handling can bypass the library's internal bounds logic, exposing adjacent memory or corrupting buffer state. No public exploit code has been identified at time of analysis, and active exploitation has not been confirmed by CISA KEV.
Signature verification bypass in the OCaml jose library (ulrikstrid/ocaml-jose) before 0.11.0 lets attackers forge valid RSA-signed JWS/JWT tokens. The RSA verify path in Jws.ml only confirmed that PKCS #1 decoding succeeded and then returned success, never performing the RSA public-key operation that actually authenticates the signature. Any attacker can craft a token with an arbitrary payload and a syntactically well-formed but cryptographically meaningless signature and have it accepted as valid; no public exploit identified at time of analysis, but the flaw is trivially exploitable once understood.
Remote denial of service in the utcp OCaml TCP userspace library before version 0.0.6 is possible via crafted out-of-order TCP segment sequences that expose a flaw in the segment reassembly logic. Unauthenticated network attackers can exploit this against any service built on the affected library, causing complete availability loss. No public exploit code or active exploitation has been identified at time of analysis.
Arbitrary file write in OCaml opam before 2.5.1 allows a malicious package to escape its intended installation scope: a destination filepath in a package's .install field can contain ../ sequences to reach parent directories and drop files outside the target prefix. Exploitation requires a user to install a crafted opam package, so it is a supply-chain/local vector rather than a remote one. Tracked as OSEC-2026-03 and fixed in opam 2.5.1; no public exploit identified at time of analysis and EPSS is negligible (0.01%).
Heap memory corruption in the OCaml runtime (before 4.14.3 and 5.x before 5.4.1) lets an attacker who can feed crafted Marshal-format data into an application's deserialization path read past buffer bounds and, through a multi-phase chain, achieve code execution. The flaw lives in the readblock() routine of runtime/intern.c, which copies blocks using attacker-controlled lengths without bounds checks. There is no public exploit identified at time of analysis and EPSS is very low (0.04%), but multiple vendors (SUSE, Red Hat) have shipped fixed packages.
Timing side-channel in mirage-crypto-ec before 2.4.0 for OCaml enables remote cryptographic key recovery by exploiting secret-dependent timing variations during NIST elliptic-curve scalar multiplication table lookups. Affected applications performing ECDH key agreement or ECDSA signing - including TLS endpoints built on this library - leak private key material through measurable latency differences. No active exploitation is confirmed (no CISA KEV listing), but the C:H CVSS impact rating accurately reflects that successful key recovery constitutes full confidentiality compromise of the cryptographic material.
Out-of-bounds read in the mirage-crypto-ec OCaml cryptographic library (versions before 2.3.0) allows low-privileged network attackers to crash or disrupt services that parse compressed elliptic curve public keys. The flaw arises from insufficient bounds checking during compressed EC point deserialization, classified under CWE-125. No public exploit has been identified at time of analysis; a vendor-released patch is available in version 2.3.0.
RSA operations in mirage-crypto-pk for OCaml before version 2.3.0 raise an undocumented exception when processing abnormally small messages during encryption or decryption. Any OCaml application - including MirageOS unikernel services - that exposes RSA operations to attacker-influenced inputs without upstream size validation can have those operations disrupted by a remote attacker with low-privilege access. No public exploit has been identified at time of analysis; the CVSS score of 4.3 (A:L only) reflects a limited, availability-focused impact with no confirmed confidentiality or integrity exposure.
ECDSA signature forgery is possible in mirage-crypto-ec before 2.2.0 for OCaml because the P256, P384, and P521 pub_of_octets functions accept 0x00 - the encoding of the elliptic curve point at infinity - as a valid public key. Any application relying on this library to verify ECDSA signatures against externally-supplied public keys can be deceived into accepting signatures crafted without knowledge of any private key. No public exploit has been identified at time of analysis, but the attack is conceptually elementary for anyone familiar with elliptic curve arithmetic.
Authenticated decryption in mirage-crypto before 2.2.0 for OCaml violates the security invariant of AEAD schemes by writing decrypted plaintext into the caller-supplied output buffer before the authentication tag is verified. When a forged tag is detected, `AES.GCM.authenticate_decrypt_into` and `Chacha20.authenticate_decrypt_into` return `false`, but the destination buffer already contains the full unverified plaintext. Applications that process buffer contents without rigidly checking the boolean return value - or where timing or compiler behavior creates subtle access windows - may consume attacker-controlled forged plaintext as if it were authenticated. No public exploit or KEV listing has been identified at time of analysis.
OCaml's Bigarray.reshape function contains an integer overflow vulnerability that permits unauthenticated local attackers to read arbitrary memory contents when processing untrusted input. Affected versions through 4.14.3 allow an attacker with local access to trigger the overflow condition, bypassing memory protections and potentially exposing sensitive data including cryptographic keys or process memory. No public exploit code or active exploitation has been confirmed at time of analysis.
The caml_ba_deserialize function in byterun/bigarray.c in the standard library in OCaml 4.06.0 has an integer overflow which, in situations where marshalled data is accepted from an untrusted source,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
OCaml compiler allows attackers to have unspecified impact via unknown vectors, a similar issue to CVE-2017-9772 "but with much less impact.". Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
Insufficient sanitisation in the OCaml compiler versions 4.04.0 and 4.04.1 allows external code to be executed with raised privilege in binaries marked as setuid, by setting the CAML_CPLUGINS,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
OCaml before 4.03.0 does not properly handle sign extensions, which allows remote attackers to conduct buffer overflow attacks or obtain sensitive information as demonstrated by a long string to the. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
OCaml 3.12.1 and earlier computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Denial of service in Robur Albatross (specifically the albatross-console component) versions 1.0.0 through 2.x before 2.7.2 lets an authenticated user who can send console subscription commands drive the albatross-console process into an unterminated loop over the unikernel log ring buffer, consuming CPU and making console access unavailable. Exploitation requires the targeted unikernel to have generated enough output to fill the 1024-line ring buffer, and the request must specify a very high or negative line count, or a timestamp earlier than every buffered message; the vendor states it is not exploitable by unauthorized clients, and the independent assessment confirms PR:L with availability-only impact (C:N/I:N/A:H). No public exploit code has been identified at time of analysis, so this is a genuine but bounded availability risk rather than a high-urgency threat.
Index mishandling in the OCaml cstruct library before 6.3.0 allows network-reachable attackers to trigger partial confidentiality, integrity, and availability impacts via crafted binary data passed to affected parsing routines. cstruct is a low-level binary buffer manipulation library used widely in OCaml network stacks and the MirageOS unikernel ecosystem; improper index handling can bypass the library's internal bounds logic, exposing adjacent memory or corrupting buffer state. No public exploit code has been identified at time of analysis, and active exploitation has not been confirmed by CISA KEV.
Signature verification bypass in the OCaml jose library (ulrikstrid/ocaml-jose) before 0.11.0 lets attackers forge valid RSA-signed JWS/JWT tokens. The RSA verify path in Jws.ml only confirmed that PKCS #1 decoding succeeded and then returned success, never performing the RSA public-key operation that actually authenticates the signature. Any attacker can craft a token with an arbitrary payload and a syntactically well-formed but cryptographically meaningless signature and have it accepted as valid; no public exploit identified at time of analysis, but the flaw is trivially exploitable once understood.
Remote denial of service in the utcp OCaml TCP userspace library before version 0.0.6 is possible via crafted out-of-order TCP segment sequences that expose a flaw in the segment reassembly logic. Unauthenticated network attackers can exploit this against any service built on the affected library, causing complete availability loss. No public exploit code or active exploitation has been identified at time of analysis.
Arbitrary file write in OCaml opam before 2.5.1 allows a malicious package to escape its intended installation scope: a destination filepath in a package's .install field can contain ../ sequences to reach parent directories and drop files outside the target prefix. Exploitation requires a user to install a crafted opam package, so it is a supply-chain/local vector rather than a remote one. Tracked as OSEC-2026-03 and fixed in opam 2.5.1; no public exploit identified at time of analysis and EPSS is negligible (0.01%).
Heap memory corruption in the OCaml runtime (before 4.14.3 and 5.x before 5.4.1) lets an attacker who can feed crafted Marshal-format data into an application's deserialization path read past buffer bounds and, through a multi-phase chain, achieve code execution. The flaw lives in the readblock() routine of runtime/intern.c, which copies blocks using attacker-controlled lengths without bounds checks. There is no public exploit identified at time of analysis and EPSS is very low (0.04%), but multiple vendors (SUSE, Red Hat) have shipped fixed packages.
Timing side-channel in mirage-crypto-ec before 2.4.0 for OCaml enables remote cryptographic key recovery by exploiting secret-dependent timing variations during NIST elliptic-curve scalar multiplication table lookups. Affected applications performing ECDH key agreement or ECDSA signing - including TLS endpoints built on this library - leak private key material through measurable latency differences. No active exploitation is confirmed (no CISA KEV listing), but the C:H CVSS impact rating accurately reflects that successful key recovery constitutes full confidentiality compromise of the cryptographic material.
Out-of-bounds read in the mirage-crypto-ec OCaml cryptographic library (versions before 2.3.0) allows low-privileged network attackers to crash or disrupt services that parse compressed elliptic curve public keys. The flaw arises from insufficient bounds checking during compressed EC point deserialization, classified under CWE-125. No public exploit has been identified at time of analysis; a vendor-released patch is available in version 2.3.0.
RSA operations in mirage-crypto-pk for OCaml before version 2.3.0 raise an undocumented exception when processing abnormally small messages during encryption or decryption. Any OCaml application - including MirageOS unikernel services - that exposes RSA operations to attacker-influenced inputs without upstream size validation can have those operations disrupted by a remote attacker with low-privilege access. No public exploit has been identified at time of analysis; the CVSS score of 4.3 (A:L only) reflects a limited, availability-focused impact with no confirmed confidentiality or integrity exposure.
ECDSA signature forgery is possible in mirage-crypto-ec before 2.2.0 for OCaml because the P256, P384, and P521 pub_of_octets functions accept 0x00 - the encoding of the elliptic curve point at infinity - as a valid public key. Any application relying on this library to verify ECDSA signatures against externally-supplied public keys can be deceived into accepting signatures crafted without knowledge of any private key. No public exploit has been identified at time of analysis, but the attack is conceptually elementary for anyone familiar with elliptic curve arithmetic.
Authenticated decryption in mirage-crypto before 2.2.0 for OCaml violates the security invariant of AEAD schemes by writing decrypted plaintext into the caller-supplied output buffer before the authentication tag is verified. When a forged tag is detected, `AES.GCM.authenticate_decrypt_into` and `Chacha20.authenticate_decrypt_into` return `false`, but the destination buffer already contains the full unverified plaintext. Applications that process buffer contents without rigidly checking the boolean return value - or where timing or compiler behavior creates subtle access windows - may consume attacker-controlled forged plaintext as if it were authenticated. No public exploit or KEV listing has been identified at time of analysis.
OCaml's Bigarray.reshape function contains an integer overflow vulnerability that permits unauthenticated local attackers to read arbitrary memory contents when processing untrusted input. Affected versions through 4.14.3 allow an attacker with local access to trigger the overflow condition, bypassing memory protections and potentially exposing sensitive data including cryptographic keys or process memory. No public exploit code or active exploitation has been confirmed at time of analysis.
The caml_ba_deserialize function in byterun/bigarray.c in the standard library in OCaml 4.06.0 has an integer overflow which, in situations where marshalled data is accepted from an untrusted source,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
OCaml compiler allows attackers to have unspecified impact via unknown vectors, a similar issue to CVE-2017-9772 "but with much less impact.". Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. No vendor patch available.
Insufficient sanitisation in the OCaml compiler versions 4.04.0 and 4.04.1 allows external code to be executed with raised privilege in binaries marked as setuid, by setting the CAML_CPLUGINS,. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
OCaml before 4.03.0 does not properly handle sign extensions, which allows remote attackers to conduct buffer overflow attacks or obtain sensitive information as demonstrated by a long string to the. Rated critical severity (CVSS 9.1), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
OCaml 3.12.1 and earlier computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.