<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 00:25:30 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329193</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329193</link>
      <description>EUVD-2026-329193</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329193</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47155</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47155</link>
      <description>&lt;p&gt;vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, vLLM&amp;#39;s revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies --revision or --code-revision can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision. This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision. This vulnerability is fixed in 0.22.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, vLLM&amp;#39;s revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies --revision or --code-revision can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision. This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision. This vulnerability is fixed in 0.22.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47155</guid>
    </item>
    <item>
      <title>GHSA-3ww4-5jv9-j5gm — vLLM's Artifact Pin Decay allows pinned deployments to load unpinned code, weights, and processors</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3ww4-5jv9-j5gm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vllm&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;vLLM&amp;#39;s revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies `--revision` or `--code-revision` can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision.&lt;/p&gt;
&lt;p&gt;This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The expected invariant is:&lt;/p&gt;
&lt;p&gt;&amp;gt; When a vLLM operator supplies a model or code revision pin, every code, config, processor, weight file, side weight, and same-repository subfolder artifact loaded as part of that model should resolve under that pin unless vLLM exposes and enforces a separate explicit pin for that artifact.&lt;/p&gt;
&lt;p&gt;Current `main` was verified affected at commit `3795d7acf431980e62e738493f437ae2a51549da`.&lt;/p&gt;
&lt;p&gt;Affected source boundaries:&lt;/p&gt;
&lt;p&gt;- `vllm/model_executor/models/registry.py:1045-1051` and `:1058-1064`
  - `_try_resolve_transformers()` passes `revision=model_config.revision` and `trust_remote_code=model_config.trust_remote_code`, but omits `code_revision=model_config.code_revision` for external `auto_map` dynamic module imports.
- `vllm/model_executor/model_loader/gguf_loader.py:58-60`
  - The direct-file GGUF form `repo/file.gguf` calls `hf_hub_download(repo_id=repo_id, filename=filename)` without pas…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vllm&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;vLLM&amp;#39;s revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies `--revision` or `--code-revision` can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision.&lt;/p&gt;
&lt;p&gt;This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The expected invariant is:&lt;/p&gt;
&lt;p&gt;&amp;gt; When a vLLM operator supplies a model or code revision pin, every code, config, processor, weight file, side weight, and same-repository subfolder artifact loaded as part of that model should resolve under that pin unless vLLM exposes and enforces a separate explicit pin for that artifact.&lt;/p&gt;
&lt;p&gt;Current `main` was verified affected at commit `3795d7acf431980e62e738493f437ae2a51549da`.&lt;/p&gt;
&lt;p&gt;Affected source boundaries:&lt;/p&gt;
&lt;p&gt;- `vllm/model_executor/models/registry.py:1045-1051` and `:1058-1064`
  - `_try_resolve_transformers()` passes `revision=model_config.revision` and `trust_remote_code=model_config.trust_remote_code`, but omits `code_revision=model_config.code_revision` for external `auto_map` dynamic module imports.
- `vllm/model_executor/model_loader/gguf_loader.py:58-60`
  - The direct-file GGUF form `repo/file.gguf` calls `hf_hub_download(repo_id=repo_id, filename=filename)` without pas…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3ww4-5jv9-j5gm</guid>
    </item>
    <item>
      <title>PYSEC-2026-2301</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2301</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vllm&lt;/p&gt;
&lt;p&gt;vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, vLLM&amp;#39;s revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies --revision or --code-revision can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision. This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision. This vulnerability is fixed in 0.22.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: vllm&lt;/p&gt;
&lt;p&gt;vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.0, vLLM&amp;#39;s revision pinning controls do not consistently apply to all artifacts loaded for a model. A deployment that supplies --revision or --code-revision can still load dynamic code, GGUF files, image processors, retrieval side weights, or same-repository subfolder weights/config from an unpinned/default revision. This is a supply-chain integrity issue for pinned vLLM deployments. Operators can believe they are serving a reviewed model revision while vLLM resolves behavior-affecting nested or sibling artifacts outside that reviewed revision. This vulnerability is fixed in 0.22.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2301</guid>
    </item>
    <item>
      <title>RHSA-2026:59138 — Red Hat Security Advisory: Red Hat AI Inference Server 3.3.6 (CUDA)</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:59138</link>
      <description>&lt;p&gt;vllm: vLLM: Arbitrary code execution via malicious HuggingFace model vllm: vLLM: Supply-chain integrity issue due to inconsistent revision pinning controls vllm: vLLM: Information disclosure via integer truncation&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;vllm: vLLM: Arbitrary code execution via malicious HuggingFace model vllm: vLLM: Supply-chain integrity issue due to inconsistent revision pinning controls vllm: vLLM: Information disclosure via integer truncation&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:59138</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1889 — vllm: Schwachstelle ermöglicht Manipulation von Daten</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1889</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in vllm ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in vllm ausnutzen, um Dateien zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1889</guid>
    </item>
  </channel>
</rss>
