5.2 (en)

"Expire Media" could overwrite a tape used by a backup in the meantime

Wed, 29 Jul 2026 12:17:00 GMT

SEP sesam v. 5.1.0.5 – (#36397) "Expire Media" could overwrite a tape used by a backup in the meantime

Problem: "Expire Media" can be triggered in the GUI from the context menu after selecting a medium. The dialog offers the additional option "Delete all metadata and re-initialize the tape", which explicitly re-initializes the medium.
If the drive is already occupied by a running backup at the time "Expire Media" is called, the re-initialization has to wait until the drive becomes free. In the meantime, the running backup may hit EOM and pick the medium selected for expiry as its next tape, writing data to it.
Only once the backup has finished does "Expire Media" actually run – re-initializing the tape that was written to in the meantime, so its data is lost.

Workaround: Make sure the selected medium's drive is not currently in use by a running backup before using "Expire Media".

Solution: Fixed in upcoming SEP sesam v. 5.2.0.25.

Restricted REST API access may allow unauthorized SQL operations

Wed, 19 Aug 2026 09:30:00 GMT

SEP sesam v. 5.1.0.15 – (#36581) Restricted REST API access may allow unauthorized SQL operations

Problem: A critical issue was discovered in SEP sesam v. 5.1.0.15 Apollon V2. Under certain conditions, users with restricted access to the SEP sesam REST API may be able to execute SQL queries through the API.

Solution: For the Artemis release, a manual fix will be available with SEP sesam v. 5.2.0.26. Please contact SEP support to obtain the fix.

Note: This issue is permanently fixed in the upcoming major release SEP sesam v. 5.3.0.

Restricted REST API access may allow unauthorized SQL operations (UPDATE)

Fri, 21 Aug 2026 18:00:00 GMT

SEP sesam v. 5.1.0.15 – (#36581) Restricted REST API access may allow unauthorized SQL operations

This is a follow up to the notification that was published on 2026-08-19.

Problem: A critical issue was discovered in SEP sesam v.5.1.0.15 Apollon V2. Under certain conditions, users with restricted access to the SEP sesam REST API may be able to execute SQL queries through the API.

Solution: To resolve this issue, please update to SEP sesam v. 5.2. It is not necessary to apply a manual fix.

Note: From version 5.2.0.26 onwards, additional security measures were implemented to prevent tampering with the SEP sesam database.