Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
CVE ID: CVE-2025-61763 State: PUBLISHED Published: 2025-10-21T20:03:13.622Z Last Updated: 2025-10-23T03:55:26.233Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) Vendors: Oracle Corporation Products: Oracle Essbase Problem Types: Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Essbase. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Essbase accessible data as well as unauthorized access to critical data or complete access to all Oracle Essbase accessible data. Description: Vulnerability in Oracle Essbase (compon
ical data or complete access to all Oracle Essbase accessible data. Description: Vulnerability in Oracle Essbase (component: Essbase Web Platform). The supported version that is affected is 21.7.3.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Essbase. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Essbase accessible data as well as unauthorized access to critical data or complete access to all Oracle Essbase accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/U
ccessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.oracle.com/security-alerts/cpuoct2025.html
CVE ID: CVE-2025-61764 State: PUBLISHED Published: 2025-10-21T20:03:14.012Z Last Updated: 2025-10-22T14:36:53.014Z Severity: MEDIUM (CVSS 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Vendors: Oracle Corporation Products: Oracle WebLogic Server Problem Types: Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle WebLogic Server accessible data. Description: Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1
Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://www.oracle.com/security-alerts/cpuoct2025.html
CVE ID: CVE-2025-61765 State: PUBLISHED Published: 2025-10-06T16:04:22.559Z Last Updated: 2025-10-22T17:13:12.129Z Severity: MEDIUM (CVSS 6.4 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L) Vendors: miguelgrinberg Products: python-socketio Problem Types: CWE-502 Description: python-socketio is a Python implementation of the Socket.IO realtime client and server. A remote code execution vulnerability in python-socketio versions prior to 5.14.0 allows attackers to execute arbitrary Python code through malicious pickle deserialization in multi-server deployments on which the attacker previously gained access to the message queue that the servers use for internal communications. When Socket.IO serv
cker previously gained access to the message queue that the servers use for internal communications. When Socket.IO servers are configured to use a message queue backend such as Redis for inter-server communication, messages sent between the servers are encoded using the `pickle` Python module. When a server receives one of these messages through the message queue, it assumes it is trusted and immediately deserializes it. The vulnerability stems from deserialization of messages using Python's `pickle.loads()` function. Having previously obtained access to the message queue, the attacker can send a python-socketio server a crafted pickle payload that executes arbitrary code during deserializa
the attacker can send a python-socketio server a crafted pickle payload that executes arbitrary code during deserialization via Python's `__reduce__` method. This vulnerability only affects deployments with a compromised message queue. The attack can lead to the attacker executing random code in the context of, and with the privileges of a Socket.IO server process. Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable. In addition to making sure standard security practices are followed in the deployment of the message queue, users of the python-socketio package can upgrade to version 5.14.0 or newer, which remove the `
nt of the message queue, users of the python-socketio package can upgrade to version 5.14.0 or newer, which remove the `pickle` module and use the much safer JSON encoding for inter-server messaging. Additional Analyst Notes: - CISA ADP Vulnrichment: - CVE Program Container: References: - https://github.com/miguelgrinberg/python-socketio/security/advisories/GHSA-g8c6-8fjj-2r4m - https://github.com/miguelgrinberg/python-socketio/commit/53f6be094257ed81476b0e212c8cddd6d06ca39a - https://www.bluerock.io/post/cve-2025-61765-bluerock-discovers-critical-rce-in-socket-io-ecosystem
CVE ID: CVE-2025-61766 State: PUBLISHED Published: 2025-10-06T16:07:04.126Z Last Updated: 2025-10-06T17:16:30.112Z Severity: MEDIUM (CVSS 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Vendors: weirdgloop Products: mediawiki-extensions-Bucket Problem Types: CWE-674 Description: Bucket is a MediaWiki extension to store and retrieve structured data on articles. Prior to version 1.0.0, infinite recursion can occur if a user queries a bucket using the `!=` comparator. This will result in PHP's call stack limit exceeding, and/or increased memory consumption, potentially leading to a denial of service. Version 1.0.0 contains a patch for the issue. Additional Analyst Notes: - CISA ADP Vulnrichme
ng to a denial of service. Version 1.0.0 contains a patch for the issue. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/weirdgloop/mediawiki-extensions-Bucket/security/advisories/GHSA-r9f2-4jh3-659j - https://github.com/weirdgloop/mediawiki-extensions-Bucket/commit/6f4a71d531cb802cdb991d2a4ca7bf8fb691defd - https://github.com/weirdgloop/mediawiki-extensions-Bucket/blob/ad704120a1660b5929fb5825db1cf85c9c77acf4/includes/Expression/MemberOfExpression.php#L34
CVE ID: CVE-2025-61768 State: PUBLISHED Published: 2025-10-06T21:54:50.656Z Last Updated: 2025-10-07T15:51:31.246Z Vendors: xuemian168 Products: kuno Problem Types: CWE-20, CWE-434, CWE-918 Description: KUNO CMS is a fully deployable full-stack blog application. In versions prior to 1.3.15, an SSRF (Server-Side Request Forgery) vulnerability exists in the Media module of the Kuno CMS administrative panel. A logged-in administrator can upload a specially crafted SVG file containing an external image reference, causing the server to initiate an outgoing connection to an arbitrary external URL. This can lead to information disclosure or internal network probing. Version 1.3.15 contains a fix fo
rary external URL. This can lead to information disclosure or internal network probing. Version 1.3.15 contains a fix for the issue. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/xuemian168/kuno/security/advisories/GHSA-4f5f-2c49-5mwm - https://github.com/xuemian168/kuno/commit/804b2909c65b16ae2063d0f992e0711aa09475e2 - https://github.com/xuemian168/kuno/releases/tag/v1.3.15
CVE ID: CVE-2025-61769 State: PUBLISHED Published: 2025-10-06T16:09:53.554Z Last Updated: 2025-10-06T17:16:13.290Z Vendors: emlog Products: emlog Problem Types: CWE-79 Description: Emlog is an open source website building system. A cross-site scripting (XSS) vulnerability in emlog up to and including version 2.5.22 allows authenticated remote attackers to inject arbitrary web script or HTML via the file upload functionality. As an authenticated user it is possible to upload .svg file that contains JavaScript code that is later being executed. Commit 052f9c4226b2c0014bcd857fec47677340b185b1 fixes the issue. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/em
ec47677340b185b1 fixes the issue. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/emlog/emlog/security/advisories/GHSA-rrf5-pv68-gpjf - https://github.com/emlog/emlog/commit/052f9c4226b2c0014bcd857fec47677340b185b1
CVE ID: CVE-2025-61770 State: PUBLISHED Published: 2025-10-07T14:30:04.552Z Last Updated: 2025-10-07T15:43:06.827Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: rack Products: rack Problem Types: CWE-400 Description: Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, `Rack::Multipart::Parser` buffers the entire multipart preamble (bytes before the first boundary) in memory without any size limit. A client can send a large preamble followed by a valid boundary, causing significant memory use and potential process termination due to out-of-memory (OOM) conditions. Remote attackers can trigger large transient memory spi
ntial process termination due to out-of-memory (OOM) conditions. Remote attackers can trigger large transient memory spikes by including a long preamble in multipart/form-data requests. The impact scales with allowed request sizes and concurrency, potentially causing worker crashes or severe slowdown due to garbage collection. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a preamble size limit (e.g., 16 KiB) or discard preamble data entirely. Workarounds include limiting total request body size at the proxy or web server level and monitoring memory and set per-process limits to prevent OOM conditions. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/rack/rack/
o prevent OOM conditions. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/rack/rack/security/advisories/GHSA-p543-xpfm-54cp - https://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e - https://github.com/rack/rack/commit/d869fed663b113b95a74ad53e1b5cae6ab31f29e - https://github.com/rack/rack/commit/e08f78c656c9394d6737c022bde087e0f33336fd
CVE ID: CVE-2025-61771 State: PUBLISHED Published: 2025-10-07T14:42:53.366Z Last Updated: 2025-10-07T17:52:09.399Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: rack Products: rack Problem Types: CWE-400 Description: Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, ``Rack::Multipart::Parser` stores non-file form fields (parts without a `filename`) entirely in memory as Ruby `String` objects. A single large text field in a multipart/form-data request (hundreds of megabytes or more) can consume equivalent process memory, potentially leading to out-of-memory (OOM) conditions and denial of service (DoS). Attackers can
valent process memory, potentially leading to out-of-memory (OOM) conditions and denial of service (DoS). Attackers can send large non-file fields to trigger excessive memory usage. Impact scales with request size and concurrency, potentially leading to worker crashes or severe garbage-collection overhead. All Rack applications processing multipart form submissions are affected. Versions 2.2.19, 3.1.17, and 3.2.2 enforce a reasonable size cap for non-file fields (e.g., 2 MiB). Workarounds include restricting maximum request body size at the web-server or proxy layer (e.g., Nginx `client_max_body_size`) and validating and rejecting unusually large form fields at the application level. Additio
Nginx `client_max_body_size`) and validating and rejecting unusually large form fields at the application level. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/rack/rack/security/advisories/GHSA-w9pc-fmgc-vxvw - https://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e - https://github.com/rack/rack/commit/d869fed663b113b95a74ad53e1b5cae6ab31f29e - https://github.com/rack/rack/commit/e08f78c656c9394d6737c022bde087e0f33336fd
CVE ID: CVE-2025-61772 State: PUBLISHED Published: 2025-10-07T15:02:09.895Z Last Updated: 2025-10-07T17:51:26.246Z Severity: HIGH (CVSS 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vendors: rack Products: rack Problem Types: CWE-400 Description: Rack is a modular Ruby web server interface. In versions prior to 2.2.19, 3.1.17, and 3.2.2, `Rack::Multipart::Parser` can accumulate unbounded data when a multipart part’s header block never terminates with the required blank line (`CRLFCRLF`). The parser keeps appending incoming bytes to memory without a size cap, allowing a remote attacker to exhaust memory and cause a denial of service (DoS). Attackers can send incomplete multipart headers t
remote attacker to exhaust memory and cause a denial of service (DoS). Attackers can send incomplete multipart headers to trigger high memory use, leading to process termination (OOM) or severe slowdown. The effect scales with request size limits and concurrency. All applications handling multipart uploads may be affected. Versions 2.2.19, 3.1.17, and 3.2.2 cap per-part header size (e.g., 64 KiB). As a workaround, restrict maximum request sizes at the proxy or web server layer (e.g., Nginx `client_max_body_size`). Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/rack/rack/security/advisories/GHSA-wpv5-97wm-hp9c - https://github.com/rack/rack/commit/589127f4
s: - https://github.com/rack/rack/security/advisories/GHSA-wpv5-97wm-hp9c - https://github.com/rack/rack/commit/589127f4ac8b5cf11cf88fb0cd116ffed4d2181e - https://github.com/rack/rack/commit/d869fed663b113b95a74ad53e1b5cae6ab31f29e - https://github.com/rack/rack/commit/e08f78c656c9394d6737c022bde087e0f33336fd
CVE ID: CVE-2025-61773 State: PUBLISHED Published: 2025-10-09T20:49:53.892Z Last Updated: 2025-10-10T14:29:33.642Z Severity: HIGH (CVSS 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) Vendors: pyload Products: pyload Problem Types: CWE-74, CWE-94, CWE-79, CWE-116 Description: pyLoad is a free and open-source download manager written in Python. In versions prior to 0.5.0b3.dev91, pyLoad web interface contained insufficient input validation in both the Captcha script endpoint and the Click'N'Load (CNL) Blueprint. This flaw allowed untrusted user input to be processed unsafely, which could be exploited by an attacker to inject arbitrary content into the web UI or manipulate request handling.
ly, which could be exploited by an attacker to inject arbitrary content into the web UI or manipulate request handling. The vulnerability could lead to client-side code execution (XSS) or other unintended behaviors when a malicious payload is submitted. user-supplied parameters from HTTP requests were not adequately validated or sanitized before being passed into the application logic and response generation. This allowed crafted input to alter the expected execution flow. CNL (Click'N'Load) blueprint exposed unsafe handling of untrusted parameters in HTTP requests. The application did not consistently enforce input validation or encoding, making it possible for an attacker to craft maliciou
lication did not consistently enforce input validation or encoding, making it possible for an attacker to craft malicious requests. Version 0.5.0b3.dev91 contains a patch for the issue. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/pyload/pyload/security/advisories/GHSA-cjjf-27cc-pvmv - https://github.com/pyload/pyload/pull/4624 - https://github.com/pyload/pyload/commit/5823327d0b797161c7195a1f660266d30a69f0ca
CVE ID: CVE-2025-61774 State: PUBLISHED Published: 2025-10-06T22:14:38.713Z Last Updated: 2025-10-07T15:53:39.103Z Vendors: pyvista Products: pyvista Problem Types: CWE-94 Description: PyVista provides 3D plotting and mesh analysis through an interface for the Visualization Toolkit (VTK). Version 0.46.3 of the PyVista Project is vulnerable to remote code execution via dependency confusion. Two pieces of code use`--extra-index-url`. But when `--extra-index-url` is used, pip always checks for the PyPI index first, and then the external index. One package listed in the code is not published in PyPI. If an attacker publishes a package with higher version in PyPI, the malicious code from the atta
not published in PyPI. If an attacker publishes a package with higher version in PyPI, the malicious code from the attacker controlled package may be pulled, leading to remote code execution and a supply chain attack. As of time of publication, a patched version is unavailable. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/pyvista/pyvista/security/advisories/GHSA-xr7f-qcjc-63rv - https://github.com/pyvista/pyvista/commit/aabfb3db2b0d4980de9e94e66272240efba4ed95 - https://github.com/pyvista/pyvista/blob/c96e1ddbe707fb7d3eb574dc3336de1a946f14a1/.devcontainer/offscreen/oncreatecommand.sh#L4 - https://github.com/pyvista/pyvista/blob/c96e1ddbe707fb7d3eb574dc
46f14a1/.devcontainer/offscreen/oncreatecommand.sh#L4 - https://github.com/pyvista/pyvista/blob/c96e1ddbe707fb7d3eb574dc3336de1a946f14a1/docker/slim.Dockerfile#L13
CVE ID: CVE-2025-61775 State: PUBLISHED Published: 2025-10-13T17:29:50.340Z Last Updated: 2025-10-16T19:49:58.342Z Vendors: Whimsies-YAT Products: Vickey Problem Types: CWE-613, CWE-770 Description: Vickey is a Misskey-based microblogging platform. A vulnerability exists in Vickey prior to version 2025.10.0 where unexpired email confirmation links can be reused multiple times to send repeated confirmation emails to a verified email address. Under certain conditions, a verified email address could receive repeated confirmation messages if the verification link was accessed multiple times. This issue may result in unintended email traffic but does not expose user data. The issue was addressed
ultiple times. This issue may result in unintended email traffic but does not expose user data. The issue was addressed in version 2025.10.0 by improving validation logic to ensure verification links behave as expected after completion. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/Whimsies-YAT/Vickey/security/advisories/GHSA-q6hp-37x8-fhm7
CVE ID: CVE-2025-61776 State: PUBLISHED Published: 2025-10-07T18:57:06.035Z Last Updated: 2025-10-07T19:25:08.775Z Severity: MEDIUM (CVSS 4.7 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N) Vendors: DependencyTrack Products: dependency-track Problem Types: CWE-522 Description: Dependency-Track is a component analysis platform that allows organizations to identify and reduce risk in the software supply chain. Prior to version 4.13.5, Dependency-Track may send credentials meant for a private NuGet repository to `api.nuget.org` via the HTTP `Authorization` header, and may disclose names and versions of components marked as internal to `api.nuget.org`. This can happen if the Dependency-Track insta
se names and versions of components marked as internal to `api.nuget.org`. This can happen if the Dependency-Track instance contains .NET components, a custom NuGet repository has been configured, the custom repository has been configured with authentication credentials, and the repository server does not provide `PackageBaseAddress` resource in its service index. The issue has been fixed in Dependency-Track 4.13.5. Some workarounds are avaialble. Disable custom NuGet repositories until the patch has been applied, invalidate the previously used credentials, and generate new credentials for usage after the patch has been applied. Additional Analyst Notes: - CISA ADP Vulnrichment: References:
credentials for usage after the patch has been applied. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/DependencyTrack/dependency-track/security/advisories/GHSA-83g2-vgqh-mgxc - https://github.com/DependencyTrack/dependency-track/releases/tag/4.13.5
CVE ID: CVE-2025-61777 State: PUBLISHED Published: 2025-10-06T16:44:27.713Z Last Updated: 2025-10-06T17:15:50.147Z Severity: CRITICAL (CVSS 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L) Vendors: FlagForgeCTF Products: flagForge Problem Types: CWE-200, CWE-284, CWE-306 Description: Flag Forge is a Capture The Flag (CTF) platform. Starting in version 2.0.0 and prior to version 2.3.2, the `/api/admin/badge-templates` (GET) and `/api/admin/badge-templates/create` (POST) endpoints previously allowed access without authentication or authorization. This could have enabled unauthorized users to retrieve all badge templates and sensitive metadata (createdBy, createdAt, updatedAt) and/or create ar
thorized users to retrieve all badge templates and sensitive metadata (createdBy, createdAt, updatedAt) and/or create arbitrary badge templates in the database. This could lead to data exposure, database pollution, or abuse of the badge system. The issue has been fixed in FlagForge v2.3.2. GET, POST, UPDATE, and DELETE endpoints now require authentication. Authorization checks ensure only admins can access and modify badge templates. No reliable workarounds are available. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/FlagForgeCTF/flagForge/security/advisories/GHSA-26rx-c53q-rjf9 - https://github.com/FlagForgeCTF/flagForge/commit/e2121c5fb7a512a49dcd87581
rge/security/advisories/GHSA-26rx-c53q-rjf9 - https://github.com/FlagForgeCTF/flagForge/commit/e2121c5fb7a512a49dcd875812c944265fb1a846
CVE ID: CVE-2025-61778 State: PUBLISHED Published: 2025-10-06T16:53:41.707Z Last Updated: 2025-10-06T17:05:33.450Z Vendors: akkadotnet Products: akka.net Problem Types: CWE-290, CWE-295, CWE-306 Description: Akka.NET is a .NET port of the Akka project from the Scala / Java community. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our `akka.remote.dot-netty.tcp` transport and this would correctly enforce private key validation on the server-side of inbound connections. Akka.Remote, however, never asked the outbound-connecting client to present ITS certificate - therefore it's possible for untrusted parties to connect to a private key'd Akka.NET cluster and beg
t ITS certificate - therefore it's possible for untrusted parties to connect to a private key'd Akka.NET cluster and begin communicating with it without any certificate. The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. Those who run Akka.NET inside a private network that they fully control or who were never using TLS in the first place are now affected by the bug. However, those who use TLS to secure their networks must upgrade to Akka.NET V1.5.52 or later. One patch forces "fail fas
owever, those who use TLS to secure their networks must upgrade to Akka.NET V1.5.52 or later. One patch forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. The second patch, a critical fix, enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. As a workaround, avoid exposing the application publicly to avoid the vulnerability having a practical impact on one's application. However, upgrading to version 1.5.52 is still recommended by the maintainers. Additional Analyst Notes: - CISA ADP Vulnrichment: References: - https://github.com/akkado