Python: CVE-2026-26030 / GHSA-xjw9-4gw8-4rqx: question on the PR:L component of the CVSS vector

Open
#14,412 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
security

Research direction

Start by reading the GHSA-xjw9-4gw8-4rqx advisory and the CVSS:3.1 vector in the issue, then review the referenced cisagov/vulnrichment#336 SSVC assessment. Done means providing a source-backed explanation of what PR:L represents in this scoring context and how that assumption relates to the Automatable value.

Written by the indexing model from the issue text.

Description

.NET python triage

Context

I'm trying to understand the reasoning behind the PR:L component in the CVSS vector for CVE-2026-26030 / GHSA-xjw9-4gw8-4rqx (InMemoryVectorStore filter RCE, fixed in python-1.39.4):

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

This isn't a request to change the score — I'm asking a downstream question about what CISA-ADP's SSVC Automatable assessment (currently no, see cisagov/vulnrichment#336) was likely built on, since CISA's own SSVC guide treats PR:L-style authentication requirements as a typical barrier to automation.

Question

What kind of privilege was PR:L meant to represent — an authenticated/permissioned call to the hosting application (something an anonymous internet user couldn't obtain), or just whatever minimal session/identity the hosting application happens to require before it will call the vector store at all, even if that's a free, unverified self-service signup?

I ask because for a common deployment pattern — a public-facing RAG chatbot where "logging in" just means starting a session with no identity verification — the practical barrier to reaching this code path may be much lower than PR:L usually implies. Knowing which assumption was used when scoring would help me understand (and pass along accurately) what the CVSS is actually saying about exploitability here.

Not urgent — mainly trying to reconcile the CVSS with the SSVC Automatable value assigned downstream. Thanks.

Dominant language
C#
Stars
28.8k
Forks
4.9k
Avg merge
2d 17h
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/semantic-kernel

All issues in microsoft/semantic-kernel

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.