https://db.gcve.eu/sightings/feed 2026-07-22T23:28:30.198113+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent sightings. https://db.gcve.eu/sighting/c6ea9215-5920-47fc-b6f6-db195252a3be/export 2026-07-22T23:28:30.216341+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "c6ea9215-5920-47fc-b6f6-db195252a3be", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26247", "type": "seen", "source": "https://bsky.app/profile/ferramentaslinux.bsky.social/post/3lun63doelc23", "content": "", "creation_timestamp": "2025-07-23T13:51:51.570923Z"} 2025-07-23T13:51:51.570923+00:00 https://db.gcve.eu/sighting/6b7aed32-6757-431e-ac00-ad935ab8043a/export 2026-07-22T23:28:30.217502+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "6b7aed32-6757-431e-ac00-ad935ab8043a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26249", "type": "seen", "source": "https://t.me/cibsecurity/17461", "content": "\u203c CVE-2020-26249 \u203c\n\nRed Discord Bot Dashboard is an easy-to-use interactive web dashboard to control your Redbot. In Red Discord Bot before version 0.1.7a an RCE exploit has been discovered. This exploit allows Discord users with specially crafted Server names and Usernames/Nicknames to inject code into the webserver front-end code. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information. This high severity exploit has been fixed on version 0.1.7a. There are no workarounds, bot owners must upgrade their relevant packages (Dashboard module and Dashboard webserver) in order to patch this issue.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-12-09T07:35:04.000000Z"} 2020-12-09T07:35:04+00:00 https://db.gcve.eu/sighting/bd85c81f-d955-4aa9-82f2-caabc743322c/export 2026-07-22T23:28:30.217588+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "bd85c81f-d955-4aa9-82f2-caabc743322c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26248", "type": "seen", "source": "https://t.me/cibsecurity/17137", "content": "\u203c CVE-2020-26248 \u203c\n\nIn the PrestaShop module \"productcomments\" before version 4.2.1, an attacker can use a Blind SQL injection to retrieve data or stop the MySQL service. The problem is fixed in 4.2.1 of the module.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-12-04T00:26:26.000000Z"} 2020-12-04T00:26:26+00:00 https://db.gcve.eu/sighting/2ba3c47b-800a-402a-adef-7b74d936af60/export 2026-07-22T23:28:30.217644+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "2ba3c47b-800a-402a-adef-7b74d936af60", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26246", "type": "seen", "source": "https://t.me/cibsecurity/17069", "content": "\u203c CVE-2020-26246 \u203c\n\nPimcore is an open source digital experience platform. In Pimcore before version 6.8.5 it is possible to modify & create website settings without having the appropriate permissions.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-12-03T07:55:39.000000Z"} 2020-12-03T07:55:39+00:00 https://db.gcve.eu/sighting/015334bb-9cae-48b4-a82c-677db143bc57/export 2026-07-22T23:28:30.217699+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "015334bb-9cae-48b4-a82c-677db143bc57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26244", "type": "seen", "source": "https://t.me/cibsecurity/17056", "content": "\u203c CVE-2020-26244 \u203c\n\nPython oic is a Python OpenID Connect implementation. In Python oic before version 1.2.1, there are several related cryptographic issues affecting client implementations that use the library. The issues are: 1) The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg. 2) JWA `none` algorithm was allowed in all flows. 3) oic.consumer.Consumer.parse_authz returns an unverified IdToken. The verification of the token was left to the discretion of the implementator. 4) iat claim was not checked for sanity (i.e. it could be in the future). These issues are patched in version 1.2.1.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-12-02T22:55:14.000000Z"} 2020-12-02T22:55:14+00:00 https://db.gcve.eu/sighting/7a5cfefb-21af-40aa-9aa1-7e2d50e68924/export 2026-07-22T23:28:30.217756+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "7a5cfefb-21af-40aa-9aa1-7e2d50e68924", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26243", "type": "seen", "source": "https://t.me/cibsecurity/16856", "content": "\u203c CVE-2020-26243 \u203c\n\nNanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed. This is fixed in versions 0.3.9.7 and 0.4.4. The following workarounds are available: 1) Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. 2) Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed. 3) Use an arena allocator for nanopb, to make sure all memory can be released afterwards.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-11-25T20:48:08.000000Z"} 2020-11-25T20:48:08+00:00 https://db.gcve.eu/sighting/8e9c6736-5f9d-42ea-ba7e-b1960cc3864f/export 2026-07-22T23:28:30.217813+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "8e9c6736-5f9d-42ea-ba7e-b1960cc3864f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26242", "type": "seen", "source": "https://t.me/cibsecurity/16839", "content": "\u203c CVE-2020-26242 \u203c\n\nGo Ethereum, or \"Geth\", is the official Golang implementation of the Ethereum protocol. In Geth before version 1.9.18, there is a Denial-of-service (crash) during block processing. This is fixed in 1.9.18.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-11-25T07:47:26.000000Z"} 2020-11-25T07:47:26+00:00 https://db.gcve.eu/sighting/01004cc8-e27e-45f0-b749-43f53d947f1d/export 2026-07-22T23:28:30.217865+00:00 cedric https://db.gcve.eu/user/cedric {"uuid": "01004cc8-e27e-45f0-b749-43f53d947f1d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2020-26241", "type": "seen", "source": "https://t.me/cibsecurity/16836", "content": "\u203c CVE-2020-26241 \u203c\n\nGo Ethereum, or \"Geth\", is the official Golang implementation of the Ethereum protocol. This is a Consensus vulnerability in Geth before version 1.9.17 which can be used to cause a chain-split where vulnerable nodes reject the canonical chain. Geth's pre-compiled dataCopy (at 0x00...04) contract did a shallow copy on invocation. An attacker could deploy a contract that writes X to an EVM memory region R, then calls 0x00..04 with R as an argument, then overwrites R to Y, and finally invokes the RETURNDATACOPY opcode. When this contract is invoked, a consensus-compliant node would push X on the EVM stack, whereas Geth would push Y. This is fixed in version 1.9.17.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2020-11-25T07:47:23.000000Z"} 2020-11-25T07:47:23+00:00