{"answers":{"affected":"1 open source package ship an affected version, including pygments-style-solarized.","exploited":"There is no known exploitation of PYSEC-2025-8 in the wild and no public exploit code.","fix":"No fix has been published for PYSEC-2025-8 yet. Limit exposure of the affected software until one is available.","what":"PYSEC-2025-8 is a vulnerability in pygments-style-solarized, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for PYSEC-2025-8 and fix it if it is affected.\n\nWhat it is: PYSEC-2025-8 is a vulnerability in pygments-style-solarized, published on 17 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of PYSEC-2025-8 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pygments-style-solarized (PyPI): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/PYSEC-2025-8/ (Markdown: https://insights.sbomify.com/PYSEC-2025-8/index.md)","id":"PYSEC-2025-8","markdown":"https://insights.sbomify.com/PYSEC-2025-8/index.md","name":"PYSEC-2025-8","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"PyPI package","requires_auth":"none","summary":"A malicious actor uploaded a non-functional package to PyPI under a previously removed name, causing potential denial of service for users installing it.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The `pygments-style-solarized` project was removed from PyPI by its owner on 2021-08-26.\nThe GitHub repository was also updated to show unmaintained, and archived on 2025-08-31.\n\nAnother user uploaded a new version, `100.10.7`, which contains non-working code,\nwith clear language that it intends to be a dependency confusion attack.\nIt also does not contain working hacking code.\n\nThe name has been prohibited on from use on PyPI on 2021-12-12.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"After the owner removed the project from PyPI, another user uploaded a new version with non-working code","id":"PYSEC-2025-8","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"pygments-style-solarized","purl":"pkg:pypi/pygments-style-solarized","source":"PYSEC-2025-8"}],"products":null,"published":"2025-03-17","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious actor uploaded a non-functional package to PyPI under a previously removed name, causing potential denial of service for users installing it.","url":"https://insights.sbomify.com/PYSEC-2025-8/"}