Agenta before 0.122.5 SSRF via Workflow Revision URL Leaks Secret Token
Affects Agenta before 0.122.5, where workspace members with EDITOR role or workflow edit rights can point workflow revision URLs at arbitrary addresses. Fixed in 0.122.5.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.122.5
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Agenta versions before 0.122.5 are affected. Attacker is a workspace member with EDITOR role or workflow edit rights. Attacker sets an arbitrary workflow revision URL that the server invokes.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Agenta before 0.122.5 contains a server-side request forgery vulnerability that allows workspace members with workflow edit rights to redirect workflow invocations by setting arbitrary revision URLs. Attackers can capture the attached secret-resolve Authorization token to read provider secrets from the vault API, or reach internal and cloud metadata addresses.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Agenta versions before 0.122.5 are affected. Attacker is a workspace member with EDITOR role or workflow edit rights. Attacker sets an arbitrary workflow revision URL that the server invokes.Upgrade to a fixed version: 0.122.5.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Agenta-AI agenta
fixed in 0.122.5
Evidence 7
- Advisory
- Advisory
- Patch
- Patch
- Repository
Show all 7 sourcesShow fewer sources
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123786
Is CVE-2026-123786 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
What does this mean?
A workspace member who can edit workflows can set a revision URL that the Agenta server then invokes. The server attaches its secret-resolve Authorization token to that request, so the token can be captured, which allows reading provider secrets from the vault API. The same server-side requests can also reach internal and cloud metadata addresses.Source: vulncheck.com, github.com, github.com
Which versions are affected by CVE-2026-123786?
agenta: before 0.122.5.Source: cve.now feed data
Am I affected, and how do I check?
Agenta versions before 0.122.5 are affected. The precondition is a workspace member holding the EDITOR role or workflow edit rights. Check the installed agenta version against 0.122.5 and review which accounts hold those roles.Source: vulncheck.com, github.com, github.com
How do I fix CVE-2026-123786?
Upgrade Agenta to 0.122.5 or later, which contains the fix.Source: vulncheck.com, github.com, github.com