<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>PoC-in-GitHub RSS</title>
    <link>https://poc-in-github.motikan2010.net/</link>
    <description>PoC auto collect from GitHub. Be careful Malware.</description>
    <lastBuildDate>Wed, 22 Jul 2026 10:04:53 +0900</lastBuildDate>

    <item>
        <title>HORKimhab/CVE-2026-50522</title>
        <link>https://github.com/HORKimhab/CVE-2026-50522</link>
        <description>[GitHub]CVE-2026-50522 - Draft</description>
        <pubDate>Wed, 22 Jul 2026 10:04:53 +0900</pubDate>
        <category>CVE-2026-50522</category>
    </item>
    <item>
        <title>CVE-2026-43499 (2026-05-21) gagaltotal/CVE-2026-43499-PoC-Scanner</title>
        <link>https://github.com/gagaltotal/CVE-2026-43499-PoC-Scanner</link>
        <description>In the Linux kernel, the following vulnerability has been resolved:

rtmutex: Use waiter::task instead of current in remove_waiter()

remove_waiter() is used by the slowlock paths, but it is also used for
proxy-lock rollback in rt_mutex_start_proxy_lock() when invoked from
futex_requeue().

In the latter case waiter::task is not current, but remove_waiter()
operates on current for the dequeue operation. That results in several
problems:

  1) the rbtree dequeue happens without waiter::task::pi_lock being held

  2) the waiter task's pi_blocked_on state is not cleared, which leaves a
     dangling pointer primed for UAF around.

  3) rt_mutex_adjust_prio_chain() operates on the wrong top priority waiter
     task

Use waiter::task instead of current in all related operations in
remove_waiter() to cure those problems.

[ tglx: Fixup rt_mutex_adjust_prio_chain(), add a comment and amend the
  	changelog ]<br/>[GitHub]CVE-2026-43499 PoC Scanner</description>
        <pubDate>Wed, 22 Jul 2026 12:34:16 +0900</pubDate>
        <category>CVE-2026-43499</category>
    </item>
    <item>
        <title>HORKimhab/CVE-2026-50055</title>
        <link>https://github.com/HORKimhab/CVE-2026-50055</link>
        <description>[GitHub]CVE-2026-50055 - Draft</description>
        <pubDate>Wed, 22 Jul 2026 13:42:46 +0900</pubDate>
        <category>CVE-2026-50055</category>
    </item>
    <item>
        <title>CVE-2026-0059 (2026-06-01) paul-goon/bootlicka-POC</title>
        <link>https://github.com/paul-goon/bootlicka-POC</link>
        <description>In multiple functions of sdp_discovery.cc, there is a possible way to achieve code execution due to a heap buffer overflow. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.<br/>[GitHub]a shitty poc utilizing CVE-2026-0059.</description>
        <pubDate>Wed, 22 Jul 2026 04:44:45 +0900</pubDate>
        <category>CVE-2026-0059</category>
    </item>
    <item>
        <title>CVE-2026-45585 (2026-05-20) boobalover7/YellowKey-Bitlocker-CVE-2026-45585</title>
        <link>https://github.com/boobalover7/YellowKey-Bitlocker-CVE-2026-45585</link>
        <description>Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as &amp;quot;YellowKey&amp;quot;. The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices.
We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security update is made available.<br/>[GitHub]Manage BitLocker recovery keys, monitor drive encryption status, and unlock volumes through a portable interface for Windows.</description>
        <pubDate>Wed, 22 Jul 2026 07:11:28 +0900</pubDate>
        <category>CVE-2026-45585</category>
    </item>
    <item>
        <title>CVE-2026-25632 (2026-02-06) lazarus0x1337/CVE-2026-25632</title>
        <link>https://github.com/lazarus0x1337/CVE-2026-25632</link>
        <description>EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.<br/>[GitHub]CVE-2026-25632 — Fix Unsafe JSON Deserialization Leading to Remote Code Execution</description>
        <pubDate>Wed, 22 Jul 2026 08:00:44 +0900</pubDate>
        <category>CVE-2026-25632</category>
    </item>
    <item>
        <title>CVE-2025-64512 (2025-11-10) MehdiChyhab/CVE-2025-64512-exploit</title>
        <link>https://github.com/MehdiChyhab/CVE-2025-64512-exploit</link>
        <description>Pdfminer.six is a community maintained fork of the original PDFMiner, a tool for extracting information from PDF documents. Prior to version 20251107, pdfminer.six will execute arbitrary code from a malicious pickle file if provided with a malicious PDF file. The `CMapDB._load_data()` function in pdfminer.six uses `pickle.loads()` to deserialize pickle files. These pickle files are supposed to be part of the pdfminer.six distribution stored in the `cmap/` directory, but a malicious PDF can specify an alternative directory and filename as long as the filename ends in `.pickle.gz`. A malicious, zipped pickle file can then contain code which will automatically execute when the PDF is processed. Version 20251107 fixes the issue.<br/>[GitHub]CVE-2025-64512 - pdfminer.six Remote Code Execution Exploit</description>
        <pubDate>Wed, 22 Jul 2026 08:46:37 +0900</pubDate>
        <category>CVE-2025-64512</category>
    </item>
    <item>
        <title>CVE-2024-27867 (2024-06-26) Hirador/pspgo-airpods-802F0130</title>
        <link>https://github.com/Hirador/pspgo-airpods-802F0130</link>
        <description>An authentication issue was addressed with improved state management. This issue is fixed in AirPods Firmware Update 6A326, AirPods Firmware Update 6F8, and Beats Firmware Update 6F8. When your headphones are seeking a connection request to one of your previously paired devices, an attacker in Bluetooth range might be able to spoof the intended source device and gain access to your headphones.<br/>[GitHub]Why AirPods stopped pairing with the PSP Go (error 0x802F0130): full reverse-engineering root-cause writeup — CVE-2024-27867</description>
        <pubDate>Wed, 22 Jul 2026 06:22:52 +0900</pubDate>
        <category>CVE-2024-27867</category>
    </item>
    <item>
        <title>CVE-2022-35914 (2022-09-20) YumeSecurity/CVE-2022-35914</title>
        <link>https://github.com/YumeSecurity/CVE-2022-35914</link>
        <description>/vendor/htmlawed/htmlawed/htmLawedTest.php in the htmlawed module for GLPI through 10.0.2 allows PHP code injection.<br/>[GitHub]my exploit for GLPI</description>
        <pubDate>Wed, 22 Jul 2026 06:08:58 +0900</pubDate>
        <category>CVE-2022-35914</category>
    </item>
    <item>
        <title>CVE-2026-43499 (2026-05-21) geecjdj/CVE-2026-43499</title>
        <link>https://github.com/geecjdj/CVE-2026-43499</link>
        <description>In the Linux kernel, the following vulnerability has been resolved:

rtmutex: Use waiter::task instead of current in remove_waiter()

remove_waiter() is used by the slowlock paths, but it is also used for
proxy-lock rollback in rt_mutex_start_proxy_lock() when invoked from
futex_requeue().

In the latter case waiter::task is not current, but remove_waiter()
operates on current for the dequeue operation. That results in several
problems:

  1) the rbtree dequeue happens without waiter::task::pi_lock being held

  2) the waiter task's pi_blocked_on state is not cleared, which leaves a
     dangling pointer primed for UAF around.

  3) rt_mutex_adjust_prio_chain() operates on the wrong top priority waiter
     task

Use waiter::task instead of current in all related operations in
remove_waiter() to cure those problems.

[ tglx: Fixup rt_mutex_adjust_prio_chain(), add a comment and amend the
  	changelog ]<br/>[GitHub]CVE-2026-43499</description>
        <pubDate>Tue, 21 Jul 2026 13:34:23 +0900</pubDate>
        <category>CVE-2026-43499</category>
    </item>
  </channel>
</rss>