borghei/Claude-Skills / engineering/senior-secops
senior-secops
FlaggedSecOps for application security, vulnerability management, compliance, and secure development. Use when implementing security controls, conducting security audits, responding to vulnerabilities, or meeting compliance requirements.
Security report
FlaggedStatic analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.
- Commit
25bf86b89c6c1e63f433a5b65e8cfcb6cf0b7ad3- Content hash
424c13678d45f0f2726292b123470f05c6b1572f786b61e34342bd2bff9e704b- Scanned
- 2026-11-17
- Scanner version
- skillxone-scan-1.0.0
- Policy version
- 0.1-draft
- Decision
- 33 open critical or high findings.
- Verification expires
- Not applicable
Findings (9 critical, 24 high, 113 medium, 13 low, 3 info)
django@2.2.0 is affected by GHSA-2gwj-7jmv-h26r: SQL Injection in Django
django@2.2.0 (GHSA-2gwj-7jmv-h26r)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-6r97-cj55-9hrq: SQL Injection in Django
django@2.2.0 (GHSA-6r97-cj55-9hrq)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-frmv-pr5f-9mcr: Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.
django@2.2.0 (GHSA-frmv-pr5f-9mcr)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-hmr4-m2h5-33qx: SQL injection in Django
django@2.2.0 (GHSA-hmr4-m2h5-33qx)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-vfq6-hq5r-27r6: Django Potential account hijack via password reset form
django@2.2.0 (GHSA-vfq6-hq5r-27r6)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-w24h-v9qh-8gxj: SQL Injection in Django
django@2.2.0 (GHSA-w24h-v9qh-8gxj)Suggested fix: Upgrade to a version without the vulnerability.
pyyaml@5.3 is affected by GHSA-6757-jp84-gxfx: Improper Input Validation in PyYAML
pyyaml@5.3 (GHSA-6757-jp84-gxfx)Suggested fix: Upgrade to a version without the vulnerability.
pyyaml@5.3 is affected by GHSA-8q59-q68h-6hv4: Improper Input Validation in PyYAML
pyyaml@5.3 (GHSA-8q59-q68h-6hv4)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-frmv-pr5f-9mcr: Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects.
django@5.2.1 (GHSA-frmv-pr5f-9mcr)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-3gh2-xw74-jmcw: SQL injection in Django
django@2.2.0 (GHSA-3gh2-xw74-jmcw)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-53qw-q765-4fww: Denial-of-service in Django
django@2.2.0 (GHSA-53qw-q765-4fww)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-6cw3-g6wv-c2xv: Infinite Loop in Django
django@2.2.0 (GHSA-6cw3-g6wv-c2xv)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-6w2r-r2m5-xq5w: Django is subject to SQL injection through its column aliases
django@2.2.0 (GHSA-6w2r-r2m5-xq5w)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-8c5j-9r9f-c6w8: Information disclosure in Django
django@2.2.0 (GHSA-8c5j-9r9f-c6w8)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-8x94-hmjh-97hq: Django vulnerable to Reflected File Download attack
django@2.2.0 (GHSA-8x94-hmjh-97hq)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-c4qh-4vgv-qc6g: Django Denial-of-service in django.utils.text.Truncator
django@2.2.0 (GHSA-c4qh-4vgv-qc6g)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-h5jv-4p7w-64jg: Django Denial-of-service in strip_tags()
django@2.2.0 (GHSA-h5jv-4p7w-64jg)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-hvmf-r92r-27hr: Django allows unintended model editing
django@2.2.0 (GHSA-hvmf-r92r-27hr)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-m6gj-h9gm-gw44: Django Incorrect Default Permissions
django@2.2.0 (GHSA-m6gj-h9gm-gw44)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-p99v-5w3c-jqq9: Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks
django@2.2.0 (GHSA-p99v-5w3c-jqq9)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-qw25-v68c-qjf3: Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
django@2.2.0 (GHSA-qw25-v68c-qjf3)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-rxjp-mfm9-w4wr: Path Traversal in Django
django@2.2.0 (GHSA-rxjp-mfm9-w4wr)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-v9qg-3j8p-r63v: Uncontrolled Recursion in Django
django@2.2.0 (GHSA-v9qg-3j8p-r63v)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-wpjr-j57x-wxfw: Data leakage via cache key collision in Django
django@2.2.0 (GHSA-wpjr-j57x-wxfw)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-wvqv-fj8w-qmhm: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
django@2.2.0 (GHSA-wvqv-fj8w-qmhm)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by GHSA-x84v-xcm2-53pg: Insufficiently Protected Credentials in Requests
requests@2.19.0 (GHSA-x84v-xcm2-53pg)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-6w2r-r2m5-xq5w: Django is subject to SQL injection through its column aliases
django@5.2.1 (GHSA-6w2r-r2m5-xq5w)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-8p8v-wh79-9r56: Django vulnerable to Uncontrolled Resource Consumption
django@5.2.1 (GHSA-8p8v-wh79-9r56)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-933h-hp56-hf7m: Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit
django@5.2.1 (GHSA-933h-hp56-hf7m)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-gvg8-93h5-g6qq: Django has an SQL Injection issue
django@5.2.1 (GHSA-gvg8-93h5-g6qq)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-hpr9-3m2g-3j9p: Django vulnerable to SQL injection in column aliases
django@5.2.1 (GHSA-hpr9-3m2g-3j9p)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-qw25-v68c-qjf3: Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows
django@5.2.1 (GHSA-qw25-v68c-qjf3)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-wvqv-fj8w-qmhm: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
django@5.2.1 (GHSA-wvqv-fj8w-qmhm)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-2m34-jcjv-45xf: XSS in Django
django@2.2.0 (GHSA-2m34-jcjv-45xf)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-68w8-qjq3-2gfm: Path Traversal in Django
django@2.2.0 (GHSA-68w8-qjq3-2gfm)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-6c3j-c64m-qhgq: XSS in jQuery as used in Drupal, Backdrop CMS, and other products
django@2.2.0 (GHSA-6c3j-c64m-qhgq)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-6c7v-2f49-8h26: Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS
django@2.2.0 (GHSA-6c7v-2f49-8h26)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-7rp2-fm2h-wchj: Django Cross-site Scripting in AdminURLFieldWidget
django@2.2.0 (GHSA-7rp2-fm2h-wchj)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-7xr5-9hcq-chf9: Django Improper Output Neutralization for Logs vulnerability
django@2.2.0 (GHSA-7xr5-9hcq-chf9)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-8qcx-xf44-272x: Django: DomainNameValidator permits newline characters that may enable HTTP header injection
django@2.2.0 (GHSA-8qcx-xf44-272x)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-95rw-fx8r-36v6: Cross-site Scripting in Django
django@2.2.0 (GHSA-95rw-fx8r-36v6)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-crhf-3pfg-w68w: Django: GDALRaster may over-read heap memory when constructed from bytes
django@2.2.0 (GHSA-crhf-3pfg-w68w)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-fr28-569j-53c4: Django Incorrect Default Permissions
django@2.2.0 (GHSA-fr28-569j-53c4)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-fvgf-6h6h-3322: Django Directory Traversal via archive.extract
django@2.2.0 (GHSA-fvgf-6h6h-3322)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-jrh2-hc4r-7jwx: Directory-traversal in Django
django@2.2.0 (GHSA-jrh2-hc4r-7jwx)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-q238-5cxm-5c9h: Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
django@2.2.0 (GHSA-q238-5cxm-5c9h)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-qm57-vhq3-3fwf: Header injection possible in Django
django@2.2.0 (GHSA-qm57-vhq3-3fwf)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-rrqc-c2jx-6jgv: Django allows enumeration of user e-mail addresses
django@2.2.0 (GHSA-rrqc-c2jx-6jgv)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-v6rh-hp5x-86rv: Potential bypass of an upstream access control based on URL paths in Django
django@2.2.0 (GHSA-v6rh-hp5x-86rv)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-xgxc-v2qg-chmh: Directory Traversal in Django
django@2.2.0 (GHSA-xgxc-v2qg-chmh)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-10.
django@2.2.0 (PYSEC-2019-10)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-11.
django@2.2.0 (PYSEC-2019-11)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-12.
django@2.2.0 (PYSEC-2019-12)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-13.
django@2.2.0 (PYSEC-2019-13)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-14.
django@2.2.0 (PYSEC-2019-14)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-15.
django@2.2.0 (PYSEC-2019-15)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-16.
django@2.2.0 (PYSEC-2019-16)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2019-79.
django@2.2.0 (PYSEC-2019-79)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2020-31.
django@2.2.0 (PYSEC-2020-31)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2020-32.
django@2.2.0 (PYSEC-2020-32)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2020-33.
django@2.2.0 (PYSEC-2020-33)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2020-34.
django@2.2.0 (PYSEC-2020-34)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2020-35.
django@2.2.0 (PYSEC-2020-35)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2020-36.
django@2.2.0 (PYSEC-2020-36)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2021-439.
django@2.2.0 (PYSEC-2021-439)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2021-6.
django@2.2.0 (PYSEC-2021-6)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2021-7.
django@2.2.0 (PYSEC-2021-7)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2021-8.
django@2.2.0 (PYSEC-2021-8)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2021-9.
django@2.2.0 (PYSEC-2021-9)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2021-98.
django@2.2.0 (PYSEC-2021-98)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2021-99.
django@2.2.0 (PYSEC-2021-99)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2022-1.
django@2.2.0 (PYSEC-2022-1)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2022-19.
django@2.2.0 (PYSEC-2022-19)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2022-190.
django@2.2.0 (PYSEC-2022-190)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2022-191.
django@2.2.0 (PYSEC-2022-191)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2022-2.
django@2.2.0 (PYSEC-2022-2)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2022-20.
django@2.2.0 (PYSEC-2022-20)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2022-3.
django@2.2.0 (PYSEC-2022-3)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2026-1297: Django allows enumeration of user e-mail addresses
django@2.2.0 (PYSEC-2026-1297)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2026-3717.
django@2.2.0 (PYSEC-2026-3717)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2026-4035: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
django@2.2.0 (PYSEC-2026-4035)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by PYSEC-2026-628: XSS in jQuery as used in Drupal, Backdrop CMS, and other products
django@2.2.0 (PYSEC-2026-628)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by GHSA-9hjg-9r4m-mvj7: Requests vulnerable to .netrc credentials leak via malicious URLs
requests@2.19.0 (GHSA-9hjg-9r4m-mvj7)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by GHSA-9wx4-h78v-vm56: Requests `Session` object does not verify requests after making first request with verify=False
requests@2.19.0 (GHSA-9wx4-h78v-vm56)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by GHSA-gc5v-m9x4-r6x2: Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function
requests@2.19.0 (GHSA-gc5v-m9x4-r6x2)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by GHSA-j8r2-6x86-q33q: Unintended leak of Proxy-Authorization header in requests
requests@2.19.0 (GHSA-j8r2-6x86-q33q)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by PYSEC-2018-28.
requests@2.19.0 (PYSEC-2018-28)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by PYSEC-2023-74.
requests@2.19.0 (PYSEC-2023-74)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by PYSEC-2026-1872: Requests vulnerable to .netrc credentials leak via malicious URLs
requests@2.19.0 (PYSEC-2026-1872)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by PYSEC-2026-1873: Requests `Session` object does not verify requests after making first request with verify=False
requests@2.19.0 (PYSEC-2026-1873)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.19.0 is affected by PYSEC-2026-2275.
requests@2.19.0 (PYSEC-2026-2275)Suggested fix: Upgrade to a version without the vulnerability.
pyyaml@5.3 is affected by PYSEC-2020-96.
pyyaml@5.3 (PYSEC-2020-96)Suggested fix: Upgrade to a version without the vulnerability.
pyyaml@5.3 is affected by PYSEC-2021-142.
pyyaml@5.3 (PYSEC-2021-142)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-5mf9-h53q-7mhq: Django has potential DoS via MultiPartParser through crafted multipart uploads
django@5.2.1 (GHSA-5mf9-h53q-7mhq)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-6426-9fv3-65x8: Django has an SQL Injection issue
django@5.2.1 (GHSA-6426-9fv3-65x8)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-7xr5-9hcq-chf9: Django Improper Output Neutralization for Logs vulnerability
django@5.2.1 (GHSA-7xr5-9hcq-chf9)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-8qcx-xf44-272x: Django: DomainNameValidator permits newline characters that may enable HTTP header injection
django@5.2.1 (GHSA-8qcx-xf44-272x)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-crhf-3pfg-w68w: Django: GDALRaster may over-read heap memory when constructed from bytes
django@5.2.1 (GHSA-crhf-3pfg-w68w)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-mjgh-79qc-68w3.
django@5.2.1 (GHSA-mjgh-79qc-68w3)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-mm6v-q8q9-pgcf.
django@5.2.1 (GHSA-mm6v-q8q9-pgcf)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-mmwr-2jhp-mc7j.
django@5.2.1 (GHSA-mmwr-2jhp-mc7j)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-mvfq-ggxm-9mc5.
django@5.2.1 (GHSA-mvfq-ggxm-9mc5)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-mwm9-4648-f68q.
django@5.2.1 (GHSA-mwm9-4648-f68q)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-pwjp-ccjc-ghwg.
django@5.2.1 (GHSA-pwjp-ccjc-ghwg)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-q238-5cxm-5c9h: Django GeoDjango vulnerable to denial of service through deeply nested geometry collections
django@5.2.1 (GHSA-q238-5cxm-5c9h)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-q95w-c7qg-hrff.
django@5.2.1 (GHSA-q95w-c7qg-hrff)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-qpc8-7fxc-cm4p.
django@5.2.1 (GHSA-qpc8-7fxc-cm4p)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-rqw2-ghq9-44m7.
django@5.2.1 (GHSA-rqw2-ghq9-44m7)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-vrcr-9hj9-jcg6.
django@5.2.1 (GHSA-vrcr-9hj9-jcg6)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-w26r-rmm8-9c29.
django@5.2.1 (GHSA-w26r-rmm8-9c29)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2025-104.
django@5.2.1 (PYSEC-2025-104)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2025-105.
django@5.2.1 (PYSEC-2025-105)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2025-106.
django@5.2.1 (PYSEC-2025-106)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2025-107.
django@5.2.1 (PYSEC-2025-107)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2025-108.
django@5.2.1 (PYSEC-2025-108)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2025-109.
django@5.2.1 (PYSEC-2025-109)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2025-47.
django@5.2.1 (PYSEC-2025-47)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-1296.
django@5.2.1 (PYSEC-2026-1296)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-197.
django@5.2.1 (PYSEC-2026-197)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-198.
django@5.2.1 (PYSEC-2026-198)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-199.
django@5.2.1 (PYSEC-2026-199)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-200.
django@5.2.1 (PYSEC-2026-200)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-201.
django@5.2.1 (PYSEC-2026-201)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-2090.
django@5.2.1 (PYSEC-2026-2090)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-2091.
django@5.2.1 (PYSEC-2026-2091)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-2092.
django@5.2.1 (PYSEC-2026-2092)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-2448.
django@5.2.1 (PYSEC-2026-2448)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-2449.
django@5.2.1 (PYSEC-2026-2449)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-3717.
django@5.2.1 (PYSEC-2026-3717)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-4035: Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing
django@5.2.1 (PYSEC-2026-4035)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-42.
django@5.2.1 (PYSEC-2026-42)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-43.
django@5.2.1 (PYSEC-2026-43)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-44.
django@5.2.1 (PYSEC-2026-44)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-45.
django@5.2.1 (PYSEC-2026-45)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-46.
django@5.2.1 (PYSEC-2026-46)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-47.
django@5.2.1 (PYSEC-2026-47)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-48.
django@5.2.1 (PYSEC-2026-48)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-49.
django@5.2.1 (PYSEC-2026-49)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-50.
django@5.2.1 (PYSEC-2026-50)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-51.
django@5.2.1 (PYSEC-2026-51)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-52.
django@5.2.1 (PYSEC-2026-52)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-53.
django@5.2.1 (PYSEC-2026-53)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-54.
django@5.2.1 (PYSEC-2026-54)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by PYSEC-2026-55.
django@5.2.1 (PYSEC-2026-55)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.32.4 is affected by GHSA-gc5v-m9x4-r6x2: Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function
requests@2.32.4 (GHSA-gc5v-m9x4-r6x2)Suggested fix: Upgrade to a version without the vulnerability.
requests@2.32.4 is affected by PYSEC-2026-2275.
requests@2.32.4 (PYSEC-2026-2275)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-3h9f-r86x-qvjx: Django: cache middleware may expose private responses when unrelated request cookies are present
django@2.2.0 (GHSA-3h9f-r86x-qvjx)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-8cjm-8mp7-r2xf: Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling
django@2.2.0 (GHSA-8cjm-8mp7-r2xf)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-923m-gv2p-w5qp: Django: has_vary_header may expose cached responses when Vary values contain whitespace
django@2.2.0 (GHSA-923m-gv2p-w5qp)Suggested fix: Upgrade to a version without the vulnerability.
django@2.2.0 is affected by GHSA-h7pc-vwp9-298g: Django: signed cookies are vulnerable to salt namespace collisions
django@2.2.0 (GHSA-h7pc-vwp9-298g)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-2mcm-79hx-8fxw: Django has Observable Timing Discrepancy
django@5.2.1 (GHSA-2mcm-79hx-8fxw)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-33mw-q7rj-mjwj: Django has Inefficient Algorithmic Complexity
django@5.2.1 (GHSA-33mw-q7rj-mjwj)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-3h9f-r86x-qvjx: Django: cache middleware may expose private responses when unrelated request cookies are present
django@5.2.1 (GHSA-3h9f-r86x-qvjx)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-4rrr-2h4v-f3j9: Django has Inefficient Algorithmic Complexity
django@5.2.1 (GHSA-4rrr-2h4v-f3j9)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-5hrc-gvxj-w55p: Django Uses Cache Containing Sensitive Information
django@5.2.1 (GHSA-5hrc-gvxj-w55p)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-7h2m-m8vj-598h: Django Uses Persistent Cookies Containing Sensitive Information
django@5.2.1 (GHSA-7h2m-m8vj-598h)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-8cjm-8mp7-r2xf: Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling
django@5.2.1 (GHSA-8cjm-8mp7-r2xf)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-923m-gv2p-w5qp: Django: has_vary_header may expose cached responses when Vary values contain whitespace
django@5.2.1 (GHSA-923m-gv2p-w5qp)Suggested fix: Upgrade to a version without the vulnerability.
django@5.2.1 is affected by GHSA-h7pc-vwp9-298g: Django: signed cookies are vulnerable to salt namespace collisions
django@5.2.1 (GHSA-h7pc-vwp9-298g)Suggested fix: Upgrade to a version without the vulnerability.
The skill ships an executable script. Review it before allowing an agent to run it.
#!/usr/bin/env python3Suggested fix: None required. Informational.
The skill ships an executable script. Review it before allowing an agent to run it.
#!/usr/bin/env python3Suggested fix: None required. Informational.
The skill ships an executable script. Review it before allowing an agent to run it.
#!/usr/bin/env python3Suggested fix: None required. Informational.
Checks run
- prompt-injection
- dangerous-commands
- credentials
- network
- file-access
- integrity
- dependencies
Checks skipped
- gitleaks: gitleaks is not installed on this host.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |