Export limit exceeded: 420979 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 420979 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (420979 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-87312 | 1 Oracle | 1 Jd Edwards Enterpriseone Tools | 2026-10-28 | 7.5 High |
| Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Enterprise Infrastructure SEC). Supported versions that are affected are 9.2.0.0-9.2.26.5. Difficult to exploit vulnerability allows low privileged attacker with network access via JDENET to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). | ||||
| CVE-2026-87310 | 1 Oracle | 1 Jd Edwards Enterpriseone Tools | 2026-10-28 | 8.8 High |
| Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Database and Comm SEC). Supported versions that are affected are 9.2.0.0-9.2.26.5. Easily exploitable vulnerability allows low privileged attacker with network access via JDENET to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). | ||||
| CVE-2025-26926 | 1 Wordpress | 1 Wordpress | 2026-10-28 | 4.3 Medium |
| Cross-Site Request Forgery (CSRF) vulnerability in Booknetic Booknetic booknetic allows Cross Site Request Forgery.This issue affects Booknetic: from n/a before 5.10.4. | ||||
| CVE-2026-99120 | 1 Linux | 2 Linux, Linux Kernel | 2026-10-28 | 4.7 Medium |
| In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes When running Hyper-V from Windows 11, KVM is seeing the SS bit set in nested page fault error codes produced for shadowed NPT. The AMD manual is unclear about when SS is set, including whether it can be set when SupervisorShadowStackEn (bit 6) is not set in the MISC_CTL field of the VMCB. Nevertheless, the unexpected SS bit causes out of bounds accesses in permission_fault(), seen as either WARNs or UBSAN reports: kernel: UBSAN: array-index-out-of-bounds in arch/x86/kvm/mmu.h:225:27 kernel: index 34 is out of range for type 'u16 [16]' (in this case, the page fault error code is 34*2=0x44, i.e. SS|U; the report shows SS|U|W happening as well). Fix the handling of unknown error codes by dropping SS and (with a WARN) any bits not among those that permission_fault() expects to receive. At the same time, given the uncertainty about when hardware sets SS, follow the processor's behavior when constructing the fault's error code, and preserve the SS bit as passed to FNAME(walk_addr_generic). While the behavior is surprising, there's a possibility that Hyper-V expects it (Hyper-V does not even enable CET unless it finds MBEC/GMET!), so retain the information when reflecting the fault to L1 instead of unconditionally discarding it. Bisection shows that this started happening with commit 687ee95c1b6d ("KVM: nSVM: enable GMET for guests"), even though SHSTK was available to guests since Linux 6.18. However, this is not because bit 1 of MISC_CTL (GMET) somehow enables reporting the SS bit; rather, it's simply that Hyper-V never uses CET unless GMET is also present. The WARN is reproducible even with gmet=0, with some hacking of kvm-unit-tests's cet.c testcase to ensure that the first access to the shadow stack triggers a page fault. | ||||
| CVE-2026-101272 | 1 Pretix | 1 Pretix | 2026-10-28 | N/A |
| The mechanism binding files generated during a shredding process to the authentication method is not working correctly and the same session token is used for all token-based API users. This is similar to an issue fixed in 2026.7.1 but was missed while creating the fix. Since the files are referred to by randomly generated UUIDs and only exist for a day, there is virtually no risk, but it renders the added protection mechanism useless. As part of the fix, we have also improved hardening of some other related code areas. | ||||
| CVE-2023-5009 | 1 Gitlab | 1 Gitlab | 2026-10-28 | 8.2 High |
| An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.2.7, all versions starting from 16.3 before 16.3.4. It was possible for an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies. This was a bypass of [CVE-2023-3932](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3932) showing additional impact. | ||||
| CVE-2023-3932 | 1 Gitlab | 1 Gitlab | 2026-10-28 | 8.2 High |
| An issue has been discovered in GitLab EE affecting all versions starting from 13.12 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. It was possible for an attacker to run pipeline jobs as an arbitrary user via scheduled security scan policies. | ||||
| CVE-2026-87309 | 1 Oracle | 1 Jd Edwards Enterpriseone Tools | 2026-10-28 | 8.1 High |
| Vulnerability in the JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Package Build SEC). Supported versions that are affected are 9.2.0.0-9.2.26.5. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all JD Edwards EnterpriseOne Tools accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 8.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H). | ||||
| CVE-2026-117858 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117857 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117856 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117855 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117854 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117853 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117852 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117851 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117850 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117849 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117848 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||
| CVE-2026-117847 | 2026-10-28 | N/A | ||
| Reserved in error; never associated with a vulnerability. | ||||