{"answers":{"affected":"","exploited":"There is no known exploitation of openSUSE-SU-2026:21728-1 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"openSUSE-SU-2026:21728-1 is a vulnerability in orthanc, published on 1 Sep 2026."},"fix_prompt":"Check this codebase for openSUSE-SU-2026:21728-1 and fix it if it is affected.\n\nWhat it is: openSUSE-SU-2026:21728-1 is a vulnerability in orthanc, published on 1 Sep 2026. \nExploitation: There is no known exploitation of openSUSE-SU-2026:21728-1 in the wild and no public exploit code.\n\nAffected product: orthanc. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/openSUSE-SU-2026-21728-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-21728-1/index.md)","id":"openSUSE-SU-2026:21728-1","markdown":"https://insights.sbomify.com/openSUSE-SU-2026-21728-1/index.md","name":"openSUSE-SU-2026:21728-1","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"unknown","non_default_config":false,"product_category":"Orthanc DICOM server","requires_auth":"unknown","summary":"Security update for Orthanc DICOM server and plugins addressing various bugs and CVEs, including unauthorized resource deletion.","user_interaction":"unknown","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for orthanc, orthanc-authorization, orthanc-postgresql, orthanc-dicomweb fixes the following issues:\n\nChanges in orthanc:\n\n- Version 1.13.0\n\n  Highlights:\n  * complete rewrite of how DICOM files are retrieved from the\n    storage area, parsed, and transcoded.\n  * The configuration file has been split into two parts\n  * The REST API has been upgraded to version 31\n  * Several security and robustness improvements have been introduced\n  * The latest value representations introduced in the DICOM standard are supported\n  * for full changelog, see NEWS\n\n- version 1.12.11\n  * Lots of Bug- and CVE-Fixes. See News for details\n\nChanges in orthanc-authorization:\n\n- Version 0.12.0\n  * Added support for inbox-links (new permission: create-inbox-links)\n\n- version 0.11.4\n  * Support new /tools/bulk-delete payload\n  * New default permissions for DICOMWeb /qido \u0026 /retrieve routes.\n\n- version 0.11.3\n  * New default permissions for jobs\n\n- Version 0.11.2\n  * Now recording audit-logs when uploading a zip.\n  * New default permissions for sending emails when sharing studies.\n  * Added support for /tools/bulk-modify and /tools/bulk-anonymize\n  * Fix: in /tools/bulk-delete, a user was able to delete resources\n    he does not have access to.\n  * Fix: in /tools/find, \"ParentSeries\" and \"ParentStudy\" fields were ignored.\n\nChanges in orthanc-postgresql:\n\n- version 10.3\n  * Wait until Orthanc has finalized its startup before executing the\n    DB HOUSEKEEPING task to avoid\n    \"Plugin trying to call the database during its initialization\" errors.\n\n- version 10.2\n  * Internal changes only:\n    - Enable linking with libpq18 (Ubuntu 26.04).\n    - Show more details when an internal error occurs.\n\n- version 10.1\n  * 'minor changes' but no changelog\n\nChanges in orthanc-dicomweb:\n\n- version 1.24\n  * Allow searching DICOM resources by \"Study ID\" in the DICOMweb client Web user interface.\n  * New configuration option \"OtherBinaryMode\" to control how OB, OD,\n    OF, OL, OV, or OW value representations are encoded in WADO-RS\n    responses. Possible values: \"BulkDataURI\" (new default),\n    \"InlineBinary\", \"ArrayOfValues\". Previous releases used the\n    \"ArrayOfValues\" mode, which was valid but could be problematic for\n    large datasets. (contribution by Yusuf Sayita, Philips)\n  * Clarified error message when trying to access a single frame from a video in WADO-RS.\n  * Fixed rendering of multiframe RGB48 images.\n  * Fix: If the metadata cache attachment is missing from disk for a series, it is now generated again.\n\n- version 1.23\n  * If calling \"/rendered\" route on a Encapsulated PDF, the plugin will now return the PDF file\n    instead of generating a 400 error.\n  * Added metrics:\n    - \"orthanc_dicomweb_wadors_average_bandwidth_per_call_mbytes_per_second_5m\" is the weighted\n      average bandwidth of each individual call to any WADO-RS route to retrieve instances, series\n      or studies. This metrics is only updated at the end of the call and averages the bandwidth\n      values that are also displayed in the logs if \"EnablePerformanceLogs\" is set to \"true\".\n    - \"orthanc_dicomweb_wadors_total_bytes_transferred\" counts the number of bytes that have\n      been returned by any WADO-RS route to retrieve instances, series, or studies. This is\n      updated while the response is returned.\n  * \"DicomWebStowClient\" jobs now have their \"Content.Resources\" and \"Content.Server\" fields\n    populated as soon as they are created, not only when they start being executed.","ecosystems":["openSUSE:Leap 16.0"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for orthanc, orthanc-authorization, orthanc-postgresql, orthanc-dicomweb","id":"openSUSE-SU-2026:21728-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"openSUSE:Leap 16.0","fixed":["1.13.0-bp160.1.1"],"introduced":["0"],"last_affected":[],"package":"orthanc","purl":"pkg:rpm/opensuse/orthanc\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21728-1"},{"ecosystem":"openSUSE:Leap 16.0","fixed":["0.12.0-bp160.1.1"],"introduced":["0"],"last_affected":[],"package":"orthanc-authorization","purl":"pkg:rpm/opensuse/orthanc-authorization\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21728-1"},{"ecosystem":"openSUSE:Leap 16.0","fixed":["1.24-bp160.1.1"],"introduced":["0"],"last_affected":[],"package":"orthanc-dicomweb","purl":"pkg:rpm/opensuse/orthanc-dicomweb\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21728-1"},{"ecosystem":"openSUSE:Leap 16.0","fixed":["10.3-bp160.1.1"],"introduced":["0"],"last_affected":[],"package":"orthanc-postgresql","purl":"pkg:rpm/opensuse/orthanc-postgresql\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21728-1"}],"products":null,"published":"2026-09-01","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Security update for Orthanc DICOM server and plugins addressing various bugs and CVEs, including unauthorized resource deletion.","url":"https://insights.sbomify.com/openSUSE-SU-2026-21728-1/"}