CVE-2026-15629
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 weakness has been identified in louisho5 picobot up to 0.2.0. Impacted is the function CreateSkill/GetSkill of the file internal/agent/tools/filesystem.go of the component Workspace Handler. Executing a manipulation can lead to link following. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. 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 confidenceThe picobot application has a link following vulnerability in the Workspace Handler (filesystem.go) affecting CreateSkill and GetSkill functions. The vulnerability allows attackers to manipulate file operations to follow symbolic links, potentially enabling unauthorized file access or modification. This is exploitable remotely with publicly available exploit code.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify picobot installation existsLocate the picobot application binary or source code. Check for filesystem.go in the codebase. Use 'which picobot' or search for the binary, and grep for 'filesystem.go' in source directories.Affected if picobot is installed and filesystem.go with Workspace Handler is present
-
Identify installed versionRun 'picobot --version' or check package manager listing. If source deployment, check git tags or version file.Affected if version cannot be determined or is unknown (vulnerable until proven otherwise)
-
Confirm Workspace Handler is accessibleInspect filesystem.go and verify CreateSkill and GetSkill functions exist. Check if the application exposes these functions via API or CLI.Affected if CreateSkill and GetSkill functions are present and accessible via network/API endpoints
-
Check for symlink validation in file operationsReview filesystem.go source code for symlink validation logic. Search for functions that validate paths before file operations (e.g., checking for 'IsDir', 'EvalSymlinks', or path traversal guards).Affected if no explicit symlink validation exists before file read/write operations in CreateSkill or GetSkill
-
Test for symlink traversal accessibilityIf you have access, create a symbolic link in the workspace directory pointing outside the intended scope, then invoke CreateSkill or GetSkill to access the target. Monitor if the symlink is followed.Affected if file operations successfully follow symbolic links to unintended locations
User is affected if picobot with filesystem.go containing CreateSkill/GetSkill is running and file operations lack symlink validation, allowing path traversal via symbolic links.
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 strict validation to prevent symlink traversal in file operations within the Workspace Handler, verifying that all file paths do not point to or traverse through symbolic links before performing read/write operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15629 — 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-15629 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