🟢 [LOW] CB-021: No HTTPS Certificate Pinning for API Calls #30

Open
opened 2026-02-20 08:50:05 +00:00 by Alpha · 0 comments

Security Finding from Audit

Parent issue: #1

Severity

LOW 🟢

CVSS Score

N/A

CWE

CWE-295 (Improper Certificate Validation)

Location

ppq/plugin.py, ollama/plugin.py, telegram/plugin.py


Description

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

## Security Finding from Audit > Parent issue: #1 ### Severity **LOW** 🟢 ### CVSS Score N/A ### CWE CWE-295 (Improper Certificate Validation) ### Location `ppq/plugin.py, ollama/plugin.py, telegram/plugin.py` --- ### Description 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*
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ultanio/cobot#30
No description provided.