Get_reports command for active scan causes SQL error

I am running the very latest community containers for GVM:

Greenbone Vulnerability Manager version 26.35.0 (DB revision 280

After starting a scan, it gives me the report_id of the scan, but when I go to fetch the report using this XML command

<get_reports report_id="3c18ed25-dd35-48ad-94dd-812c847bf32a" details="1"/>

it fails, producing this log output from gvmd:

gvmd-1  | md manage:WARNING:2026-08-01 08h46.57 utc:15108: sql_exec_internal: PQexec failed: ERROR:  column "severity_error" does not exist
gvmd-1  | LINE 1: ...) FROM results WHERE report = 459 AND severity != SEVERITY_E...
gvmd-1  |                                                              ^
gvmd-1  |  (7)
gvmd-1  | md manage:WARNING:2026-08-01 08h46.57 utc:15108: sql_exec_internal: SQL: SELECT count (DISTINCT nvt) FROM results WHERE report = 459 AND severity != SEVERITY_ERROR;
gvmd-1  | md manage:WARNING:2026-08-01 08h46.57 utc:15108: sql_x: sql_exec_internal failed
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x14a479) [0x55fbeb85a479]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x3fdf0) [0x7f60d7a14df0]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x9495c) [0x7f60d7a6995c]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x12) [0x7f60d7a14cc2]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(abort+0x22) [0x7f60d79fd4ac]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x155494) [0x55fbeb865494]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0xe2a31) [0x55fbeb7f2a31]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0xe654d) [0x55fbeb7f654d]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x7bbde) [0x55fbeb78bbde]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x62612) [0x7f60d7d10612]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_markup_parse_context_parse+0xc12) [0x7f60d7d11312]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x93e71) [0x55fbeb7a3e71]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x14fadc) [0x55fbeb85fadc]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x149fd1) [0x55fbeb859fd1]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x14a6b1) [0x55fbeb85a6b1]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x14ea26) [0x55fbeb85ea26]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) [0x7f60d79feca8]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f60d79fed65]
gvmd-1  | md   main:MESSAGE:2026-08-01 08h46.57 utc:15108: BACKTRACE: gvmd(+0x59b01) [0x55fbeb769b01]
gvmd-1  | md manage:MESSAGE:2026-08-01 08h46.57 utc:15108: Received Aborted signal
1 Like

Looks like this is the same issue as https://forum.greenbone.net/t/gvmd-26-35-0-crashes-after-scan-reaches-done-column-severity-error-does-not-exist-task-set-to-interrupted/22433.

Yes, the issue you mention seems to be the same issue as referenced by cfi here.

1 Like

Fixed with fix: include severity constant in report SQL by ozgen · Pull Request #3077 · greenbone/gvmd · GitHub and Release gvmd 26.36.0 · greenbone/gvmd · GitHub

3 Likes