CVE-2026-6129
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was detected in zhayujie chatgpt-on-wechat CowAgent up to 2.0.4. This affects an unknown function of the component Agent Mode Service. Performing a manipulation results in missing authentication. The attack can be initiated remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA missing authentication vulnerability exists in the Agent Mode Service component of CowAgent (chatgpt-on-wechat) up to version 2.0.4. Remote attackers can access unknown functions without any authentication credentials, effectively bypassing security controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify CowAgent installationLocate the chatgpt-on-wechat installation directory on the system. Check for files such as cowagent.py, agent.py, or a directory named 'cowagent' or 'agent' within the project structure.Affected if The software is present on the system and is the CowAgent (chatgpt-on-wechat) application.
-
Determine installed versionCheck the version file, setup.py, requirements.txt, or git tags within the installation directory. Compare the version number to 2.0.4 using semantic version comparison.Affected if The installed version is 2.0.4 or any earlier version.
-
Verify Agent Mode is enabledExamine configuration files (config.py, config.json, .env, or similar) for settings related to 'agent_mode', 'agent', or 'Agent Mode Service'. Look for boolean flags or enable parameters.Affected if Agent Mode is enabled in the configuration or running as an active service.
-
Check network exposure of Agent Mode ServiceReview network binding settings, firewall rules, or container/network configurations to determine if the Agent Mode Service port or endpoint is exposed to network interfaces other than localhost.Affected if The Agent Mode Service is accessible over the network without authentication controls.
-
Inspect authentication configurationExamine authentication-related settings in config files, environment variables, or code for the Agent Mode Service endpoint. Look for 'auth', 'authentication', 'token', 'password', or 'credential' settings.Affected if No authentication is required or configured for the Agent Mode Service functions.
A user is affected if CowAgent (chatgpt-on-wechat) version 2.0.4 or earlier is installed with Agent Mode Service enabled and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication checks on all Agent Mode Service functions. Until a vendor patch is available, restrict network exposure and monitor for unauthorized access attempts.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6129 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data