Vulnerabilities in pkg:pypi/semantic-router

PACKAGE
Share
Advisory Summary

GHSA-98x5-vq43-vc5p is a CRITICAL semantic-router exposed to compromised litellm vulnerability (CWE-506: Embedded Malicious Code) affecting Semantic router libraries in the PyPI ecosystem. The issue involves semantic-router exposed to compromised litellm wheel (cve-2026-42208) via unbounded transitive pin. Remediation is available by upgrading affected packages to version 0.1.15.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/semantic-router

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/semantic-router. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-98x5-vq43-vc5p - CRITICAL semantic-router exposed to compromised litellm wheel (CVE-2026-42208) via unbounded transitive pin

GHSA-98x5-vq43-vc5p at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-98x5-vq43-vc5p
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Semantic router
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-98x5-vq43-vc5p

To remediate this vulnerability, upgrade all affected Semantic router dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

semantic-router fixed: 0.1.15 
pip install semantic-router>=0.1.15
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show semantic-router

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-98x5-vq43-vc5p, inspect your installed packages using pip:

pip show semantic-router

Analyze the terminal output to locate any version of Semantic router in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.15), your application is affected.

Note: The pip show semantic-router command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Semantic router, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact semantic-router versions 0.1.8 through 0.1.14 declare `litellm>=1.61.3` with no upper bound. During the window in which `litellm==1.82.8` was the latest release on PyPI, a fresh install of any affected semantic-router version could resolve to that compromised wheel. The malicious `litellm==1.82.8` wheel ships a `litellm_init.pth` file that executes on Python interpreter startup — no import required. It collects and exfiltrates: - Process environment variables - AWS / GCP / Azure credentials - SSH keys, Kubernetes configs, shell history - Database credentials and CI/CD secrets - Cryptocurrency wallets Stage-two payload encrypts the collected data (AES-256 + embedded RSA pubkey) and POSTs it to `https://models.litellm.cloud/`. See upstream: [BerriAI/litellm#24512](https://github.com/BerriAI/litellm/issues/24512) and [CVE-2026-42208](https://www.cve.org/CVERecord?id=CVE-2026-42208). ## Patches Fixed in **semantic-router 0.1.15**, which raises the floor to `litellm>=1.83.7`. ## Workarounds If developers cannot upgrade immediately: - Pin `litellm>=1.83.7,!=1.82.8` explicitly in their own project. - Audit `site-packages/` for `litellm_init.pth` and delete if present. - Rotate any credentials reachable from environments where an affected install ran. ## Credit Upstream report and triage by the litellm maintainers — see issue [#24512](https://github.com/BerriAI/litellm/issues/24512). One caveat before publishing CVE-2026-42208 specifically names 1.82.8. Pip's resolver picks "latest matching", so the real affected blast radius for semantic-router is users who ran pip install during the window that 1.82.8 was on PyPI — not everyone who ever installed 0.1.8–0.1.14. The advisory is still correct (an affected install could have pulled the bad wheel), but consider whether a Severity: Critical / Exploitability: time-bounded note would help downstream readers understand the exposure model.

GHSA-98x5-vq43-vc5p Affected Semantic router Versions

1 component(s)
Fixed Versions:
0.1.15
Product / Package Ecosystem Affected Versions Fixed Version
semantic-router
pypi/semantic-router
PyPI
≥ 0.1.8
< 0.1.15
0.1.15

References

GitHub Advisory / Wiki ADVISORY
https://github.com/aurelio-labs/semantic-router/security/advisories/GHSA-98x5-vq43-vc5p
Semantic router Source Repository REPOSITORY
https://github.com/aurelio-labs/semantic-router

Frequently Asked Questions

What is GHSA-98x5-vq43-vc5p?
GHSA-98x5-vq43-vc5p is a security vulnerability in Semantic router involving semantic-router exposed to compromised litellm wheel (CVE-2026-42208) via unbounded transitive pin under CWE-506: Embedded Malicious Code.
Which Semantic router versions are affected?
Affected versions include releases prior to 0.1.15 across affected packages: semantic-router.
What version fixes GHSA-98x5-vq43-vc5p?
Upgrading to 0.1.15 (or the latest patched release for your respective branch) resolves the vulnerability.
Is semantic-router affected?
Yes, semantic-router is affected in releases prior to 0.1.15. Upgrade your dependency to 0.1.15 or later.
What CWE is associated with GHSA-98x5-vq43-vc5p?
GHSA-98x5-vq43-vc5p is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check PyPI dependencies for GHSA-98x5-vq43-vc5p?
Run the dependency tree command: 'pip show semantic-router'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-98x5-vq43-vc5p",
  "modified" : "2026-06-26T20:51:20Z",
  "published" : "2026-06-26T20:51:20Z",
  "aliases" : [ ],
  "summary" : "semantic-router exposed to compromised litellm wheel (CVE-2026-42208) via unbounded transitive pin",
  "details" : "## Impact\nsemantic-router versions 0.1.8 through 0.1.14 declare `litellm>=1.61.3` with no upper bound. During the window in which `litellm==1.82.8` was the latest release on PyPI, a fresh install of any affected semantic-router version could resolve to that compromised wheel.\n\nThe malicious `litellm==1.82.8` wheel ships a `litellm_init.pth` file that executes on Python interpreter startup — no import required. It collects and exfiltrates:\n- Process environment variables\n- AWS / GCP / Azure credentials\n- SSH keys, Kubernetes configs, shell history\n- Database credentials and CI/CD secrets\n- Cryptocurrency wallets\n\nStage-two payload encrypts the collected data (AES-256 + embedded RSA pubkey) and POSTs it to `https://models.litellm.cloud/`.\n\nSee upstream: [BerriAI/litellm#24512](https://github.com/BerriAI/litellm/issues/24512) and [CVE-2026-42208](https://www.cve.org/CVERecord?id=CVE-2026-42208).\n\n## Patches\nFixed in **semantic-router 0.1.15**, which raises the floor to `litellm>=1.83.7`.\n\n## Workarounds\nIf developers cannot upgrade immediately:\n- Pin `litellm>=1.83.7,!=1.82.8` explicitly in their own project.\n- Audit `site-packages/` for `litellm_init.pth` and delete if present.\n- Rotate any credentials reachable from environments where an affected install ran.\n\n## Credit\nUpstream report and triage by the litellm maintainers — see issue [#24512](https://github.com/BerriAI/litellm/issues/24512).\n\nOne caveat before publishing\n\nCVE-2026-42208 specifically names 1.82.8. Pip's resolver picks \"latest matching\", so the real affected blast radius for semantic-router is users who ran pip install during the window that 1.82.8 was on PyPI — not everyone who ever installed 0.1.8–0.1.14. The advisory is still correct (an affected install could have pulled the bad wheel), but consider whether a Severity: Critical / Exploitability: time-bounded note would help downstream readers understand the exposure model.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "semantic-router"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.1.8"
      }, {
        "fixed" : "0.1.15"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/aurelio-labs/semantic-router/security/advisories/GHSA-98x5-vq43-vc5p"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/aurelio-labs/semantic-router"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T20:51:20Z",
    "nvd_published_at" : null
  }
}