Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Bug: exports.vulns() and exports.was() still send the vpr_v2_score filter, which the API removed on 2026-10-01

Aperta
  • Qualcosa non va?
#1,054 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@lanz ci sta già lavorando.

Dal 29/10/2026.

  • #1055 di @lanz — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
python
Ambito
api

Direzione di ricerca

Start by reading the exports.vulns() and exports.was() implementations and their tests, which the issue identifies as the affected entry points. Check how export filters are assembled and how existing argument deprecations are handled; verify both methods translate vpr_v2_score, warn callers, and reject using it together with vpr_score. The linked open pull request indicates work is already underway.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Describe the bug

Tenable removed the vpr_v2_score filter from the Vulnerability Management and Web App Scanning export APIs on 2026-10-01. pyTenable still accepts vpr_v2_score in tio.exports.vulns() and tio.exports.was() and sends it in the request, so every export that uses it now fails:

tenable.errors.BadRequestError: [400: POST] https://cloud.tenable.com/vulns/export
  body=b'{"code":"BAD_REQUEST_UNKNOWN_PROPERTY","message":"Unknown property \'vpr_v2_score\' detected in the payload. ..."}'

Tenable announced the removal in three changelogs:

Date Changelog What it says
2026-04-17 Vulnerability Priority Rating: Transition to VPR Version 2 vpr_v2_score will be deprecated. Use vpr_score, which reflects the updated VPR model from July 1, 2026.
2026-06-24 Reminder: Vulnerability Priority Rating (VPR) Version 2 Transition on July 1 Reminder of the transition.
2026-09-10 Final Reminder: vpr_v2 Fields Removed from Exports on October 1 vpr_v2_score and plugin.vpr_v2 are removed from both export endpoints on 2026-10-01. vpr_score reflects the enhanced VPR model.

The Export vulnerabilities and Export findings reference pages no longer list vpr_v2_score, and both carry a caution note that it was removed.

To Reproduce

from tenable.io import TenableIO

tio = TenableIO(access_key='...', secret_key='...')
tio.exports.vulns(vpr_v2_score={'gte': 7.0})   # BadRequestError: 400 BAD_REQUEST_UNKNOWN_PROPERTY
tio.exports.was(vpr_v2_score={'gte': 7.0})     # same

Expected behavior

vpr_score now uses the same VPR v2 model that vpr_v2_score used, so existing scripts should keep working:

  • Translation: the vpr_v2_score argument is sent to the API as vpr_score, with a DeprecationWarning that tells callers to switch to vpr_score.
  • Both arguments: passing vpr_score and vpr_v2_score together raises a clear error.

Workaround

Pass the same value as vpr_score instead:

tio.exports.vulns(vpr_score={'gte': 7.0})

System Information:

  • OS: any
  • Architecture: any
  • Version: pyTenable 26.10.1 and earlier

Additional context

Confirmed against the live API in several environments: vpr_v2_score returns 400 BAD_REQUEST_UNKNOWN_PROPERTY for both vulnerability and WAS exports, while vpr_score is accepted.

Lingua principale
Python
Stelle
416
Fork
190
Merge medio
3g 20h
PR unite (30g)
12

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tenable/pyTenable

Tutte le issue di tenable/pyTenable

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.