# Safe Codex Prompt: CVE-2026-100603

Prepare a defensive remediation plan for CVE-2026-100603.

Use only the public-safe context below unless the user separately provides repo context.

Source summary: NVD: ClawHub (openclaw/clawhub) application/backend contains a flaw in the skill report moderation flow: four distinct ordinary authenticated accounts can report a visible skill and trigger automatic hiding (moderationStatus: hidden) of that skill from the catalog... NVD: Because the reporter quota counts only reports filed against visible targets, the same accounts can repeat the process against additional skills; official skills are not exempt. NVD: The issue was confirmed at revision cbfee7343ddc867316dd9b3de6fa8856730f9f41; the complete historical affected range was not established.
Affected vendor/product: unknown / unknown
Risk context: {'severity': 'HIGH', 'cvss_score': 8.7, 'cvss_label': 'HIGH', 'epss_percentile': 0.19906, 'kev_status': 'not_listed', 'risk_flags': ['CVSS HIGH', 'official reference present']}
Remediation context: {'recommended_route': 'vendor_patch_or_mitigation', 'reference_status': 'official_reference_present', 'patch_status': 'requires_confirmation', 'fixed_versions': [], 'mitigation_notes': ['Remediation reference present; patch status requires confirmation in the linked advisory.', 'Patch status requires confirmation from the linked advisory or official source.']}

Human checklist:
- Confirm whether the listed product or package is present.
- Confirm affected version.
- Review vendor advisory or official source.
- Confirm patch, fixed version, mitigation, workaround, or monitor-only decision.
- Confirm exposure.
- Document remediation status.

Allowed actions:
- summarize vendor guidance
- prepare a defensive remediation plan
- identify affected dependencies only when repo context is separately provided by the user
- suggest tests and validation steps
- document human verification questions

Disallowed actions:
- generate offensive code
- provide payloads
- scan external targets
- change production systems
- merge or deploy changes
- create GitHub issues or pull requests without explicit separate approval

Acceptance criteria:
- Affected product or dependency presence is confirmed by a human.
- Affected version is confirmed or marked not applicable.
- Official advisory or source reference is reviewed.
- Patch, fixed version, mitigation, workaround, or monitor-only decision is documented.
- Validation steps are proposed without external scanning or production mutation.

You may prepare a defensive remediation plan.
You may summarize vendor guidance.
You may identify affected dependencies only if repo context is separately provided by the user.
You may suggest tests and validation steps.
You must not generate offensive code.
You must not provide payloads.
You must not scan external targets.
You must not change production systems.
You must not merge or deploy.
Human approval is required.