🟢 [LOW] CB-021: No HTTPS Certificate Pinning for API Calls #30
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Competitor
Kind/Documentation
Kind/Enhancement
Kind/Epic
Kind/Feature
Kind/Security
Kind/Story
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Scope/Core
Scope/Cross-Plugin
Scope/Plugin-System
Scope/Single-Plugin
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ultanio/cobot#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Security Finding from Audit
Severity
LOW 🟢
CVSS Score
N/A
CWE
CWE-295 (Improper Certificate Validation)
Location
ppq/plugin.py, ollama/plugin.py, telegram/plugin.pyDescription
All HTTP clients (httpx) use default TLS settings without certificate pinning.
While httpx validates certificates by default, adding certificate pinning for the PPQ API and Telegram API would provide defense-in-depth against MITM attacks in compromised network environments.
Recommendation
Add certificate pinning for critical API endpoints.
From: Cobot Whitebox Security Audit (February 14, 2026)
Finding ID: CB-021