<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>appsec.fyi — semgrep</title>
  <link>https://appsec.fyi/tools.html#semgrep</link>
  <description>Curated semgrep resources from appsec.fyi</description>
  <language>en-us</language>
  <atom:link href="https://appsec.fyi/feeds/tool/semgrep.xml" rel="self" type="application/rss+xml"/>
  <lastBuildDate>Sun, 07 Jun 2026 04:05:35 +0000</lastBuildDate>
  <managingEditor>carl@chs.us (Carl Sampson)</managingEditor>
  <item>
    <title>tj-actions/changed-files Compromised - Semgrep</title>
    <link>https://semgrep.dev/blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/</link>
    <guid isPermaLink="true">https://semgrep.dev/blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/</guid>
    <description>Semgrep rule for detecting compromised GitHub Actions, specifically targeting `tj-actions/changed-files` and `reviewdog/action-setup@v1`. This action, `tj-actions/changed-files`, was previously compromised and may have leaked secrets. The rule helps identify usages of these actions within CI pipelines, enabling prompt remediation and security audits. Users can run this rule locally or within the Semgrep AppSec Platform in blocking mode to prevent further compromise.</description>
    <category domain="tool">semgrep</category>
    <category domain="difficulty">news</category>
    <pubDate>Thu, 16 Apr 2026 21:04:58 +0000</pubDate>
  </item>
  <item>
    <title>Insecure Deserialization in Python | Semgrep</title>
    <link>https://semgrep.dev/docs/learn/vulnerabilities/insecure-deserialization/python</link>
    <guid isPermaLink="true">https://semgrep.dev/docs/learn/vulnerabilities/insecure-deserialization/python</guid>
    <description>Library for detecting insecure deserialization vulnerabilities in Python code, focusing on the dangers of libraries like `pickle`, `dill`, `jsonpickle`, and `shelve` when processing untrusted input. It highlights how these libraries can lead to remote code execution and provides examples of exploitation, including a demonstration with `pickle.dumps` and `os.system`. The library&#x27;s rules identify data flow from untrusted sources to sensitive deserialization functions, offering practical recommendations to avoid risks such as avoiding `pickle` for untrusted data, using safer alternatives like JSON or `PyYAML`&#x27;s `safe_load`, and integrating Semgrep scans into CI pipelines. Specific mitigations for Django, NumPy, and PyTorch are also mentioned.</description>
    <category domain="tool">semgrep</category>
    <category domain="difficulty">intermediate</category>
    <pubDate>Fri, 03 Apr 2026 15:56:33 +0000</pubDate>
  </item>
  <item>
    <title>Semgrep</title>
    <link>https://semgrep.dev/s/chegg:log4j2_tainted_argument?mc_cid=6b70dd5f33&amp;mc_eid=45008603ab</link>
    <guid isPermaLink="true">https://semgrep.dev/s/chegg:log4j2_tainted_argument?mc_cid=6b70dd5f33&amp;mc_eid=45008603ab</guid>
    <description>Semgrep</description>
    <category domain="tool">semgrep</category>
    <category domain="difficulty">beginner</category>
    <pubDate>Mon, 13 Dec 2021 16:12:00 +0000</pubDate>
  </item>
</channel>
</rss>