# Safe Codex Prompt: CVE-2026-61748

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

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

Source summary: NVD: InvenTree is an Open Source Inventory Management System. NVD: Prior to 1.4.0, ReportPrint at POST /api/report/print/ and LabelPrint at POST /api/report/label/print/ require authentication but do not call users.permissions.check_user_permission for the caller's per-model view role before selecting objects by primary key... NVD: Because default templates exist for major business models and DataOutput stores the generated artifact for the requesting user, a role-less or unrelated-role account can enumerate object identifiers and download reports containing purchase, sales, part...
Affected vendor/product: unknown / unknown
Risk context: {'severity': 'MEDIUM', 'cvss_score': 4.3, 'cvss_label': 'MEDIUM', 'epss_percentile': None, 'kev_status': 'not_listed', 'risk_flags': ['official reference present']}
Remediation context: {'recommended_route': 'vendor_patch_or_mitigation', 'reference_status': 'official_reference_present', 'patch_status': 'confirmed', 'fixed_versions': ['1.4.0'], 'mitigation_notes': ['Patch confirmed by source text; fixed version context: 1.4.0..']}

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.