PLEASE don't spread misinformation. Debian releases every 2 years (usually summer of odd years). During the summer of even years, Ubuntu takes what is in debian, makes a copy, and calls it their release. Thus they leapfrog. For python specificall, the main maintainer is even the same person in both. It's not possible for Debian to "lag behind quite considerably". Here's the current situation:

  dima@shorty:~$ rmadison python3
  python3    | 3.9.2-3       | oldoldstable | amd64, arm64, armhf, i386
  python3    | 3.11.2-1+b1   | oldstable    | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
  python3    | 3.13.5-1      | stable       | amd64, arm64, armel, armhf, i386, ppc64el, riscv64, s390x
  python3    | 3.14.7-3      | testing      | amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x
  python3    | 3.14.8-1      | unstable     | amd64, arm64, armhf, i386, loong64, ppc64el, riscv64, s390x

  dima@shorty:~$ rmadison -u ubuntu python3
   python3 | 3.4.0-0ubuntu2    | trusty             | amd64, arm64, armhf, i386, powerpc, ppc64el
   python3 | 3.5.1-3           | xenial             | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   python3 | 3.6.5-3           | bionic             | amd64, arm64, armhf, i386, ppc64el, s390x
   python3 | 3.6.7-1~18.04     | bionic-updates     | amd64, arm64, armhf, i386, ppc64el, s390x
   python3 | 3.8.2-0ubuntu2    | focal              | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.10.4-0ubuntu2   | jammy              | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.10.6-1~22.04    | jammy-security     | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.10.6-1~22.04.1  | jammy-updates      | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.10.6-1~22.04.2  | jammy-proposed     | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.12.3-0ubuntu1   | noble              | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.12.3-0ubuntu2.1 | noble-security     | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.12.3-0ubuntu2.1 | noble-updates      | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.12.3-0ubuntu2.2 | noble-proposed     | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.14.3-0ubuntu2   | resolute           | amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.14.7-3          | stonking           | amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.14.7-3          | tenacious          | amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x
   python3 | 3.14.8-1          | tenacious-proposed | amd64, amd64v3, arm64, armhf, i386, ppc64el, riscv64, s390x

The ubuntu server reporting this is super slow (one of a million paper cuts you suffer when you use ubuntu instead of debian). The latest Debian stable has 3.13.5 as you say. The latest ubuntu lts release (i.e. what anybody actually uses) was released a year later, and has 3.14.3. Next summer, Debian will be ahead. Also note that the current bleeding-edge ubuntu is 3.14.8-1, which is exactly the same as the bleeding-edge debian. Because they're copies of one another