Skip to main content
← Vulnerabilities

agentscope-ai AgentScope Agent Service deps.py get_current_user_id missing authentication

6.9MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

Published
Last modified
24/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The AgentScope Agent Service from agentscope-ai (up to version 2.0.11) has a flaw in its user identification function, where the X-User-ID header is trusted without proper authentication. An attacker can reach it remotely over the network without logging in, which can affect the confidentiality, integrity, and availability of the service.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

A vulnerability has been found in agentscope-ai AgentScope up to 2.0.11. This impacts the function get_current_user_id of the file src/agentscope/app/deps.py of the component Agent Service. Such manipulation of the argument X-User-ID leads to missing authentication. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Apply the patch listed under Evidence.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • agentscope-ai AgentScope

    2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.0.10, 2.0.11

Evidence 8

  1. Advisory
  2. Advisory
  3. Advisory
  4. Advisory
  5. Patch
Show all 8 sourcesShow fewer sources
  1. Exploit
  2. Report
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123024

Is CVE-2026-123024 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-123024?

AgentScope: versions 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 and 7 more.Source: cve.now feed data