agent-framework 1.26.1 and 1.26.2 contain credential-stealing code
Published Sources: OSV
What is affected, what to do
The available sources name no fixed version. Check the vendor guidance and the linked original advisory.
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
—
XIEM Effective CVSS
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Not rated
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
agent-framework versions 1.26.1 and 1.26.2 were uploaded to PyPI on 2026-11-17
without authorization, as wheel-only releases repackaged from the legitimate 1.26.0 wheel.
Both added a .pth file, which runs the payload on every Python interpreter start
in the environment where the package is installed, without needing an import.
The payload forks a background process that collects:
- environment variables matching TOKEN, SECRET, KEY, AZURE, AWS, GITHUB, OPENAI and CI names
- credential files such as
~/.azure,pip.conf,.npmrc,.netrc,.git-credentials, Docker config, the Hugging Face token, Azure DevOps agent.credentialsand.envfiles under/appand/workspace - secrets from other processes'
/proc/*/environ - Azure DevOps OIDC tokens (via
SYSTEM_OIDCREQUESTURIandSYSTEM_ACCESSTOKEN) - Azure managed identity tokens for ARM, Graph, Key Vault, Storage, ACR, Azure DevOps and AzureADTokenExchange, plus IMDS instance metadata Version 1.26.2 also requests GitHub Actions OIDC tokens and collects runner temp files. Collected data is compressed and POSTed to a webhook.site URL.
Indicators of compromise:
- 1.26.1:
agent_framework_meta.pthandagent_framework_meta/_telemetry.py; wheel sha256 d27fa34414e6201d5e03e559ef634f020057554d7b3f4898dd5d7cd3e989e110 - 1.26.2:
af_runtime_diag.pthandaf_runtime_diag.py; wheel sha256 3d20a8bc91351a9a16b6db243b848ceca0206b7a8623b02d2af553a9c9f7e0a9 - Exfiltration: hxxps://webhook[.]site/d381fd80-ec62-42ad-8f5c-d1b15103c9bb?t=telemetry
- User-Agent:
af-runtime-diagnostics/1(1.26.1),runtime-diagnostics/1(1.26.2) - Environment variable
_AF_TELset in child processes
Any system or CI job that installed either version should be treated as compromised. Rotate every credential reachable from it, including cloud identities, CI tokens and package registry tokens, and review cloud and CI audit logs for their use.
PyPI Security worked with Microsoft to review the project's accounts and complete remediation steps. Both versions have been removed from PyPI. Version 1.26.0 is not affected.