diff --git a/jdk-updates-jdk22u-jdk-22+36.tar.gz b/jdk-updates-jdk22u-jdk-22.0.2+9.tar.gz
similarity index 82%
rename from jdk-updates-jdk22u-jdk-22+36.tar.gz
rename to jdk-updates-jdk22u-jdk-22.0.2+9.tar.gz
index 182423ff019d0a51921cbc87d42515ff6a0ad1f4..7994798de11b7acfa5ff7089aef7fa213c9b3477 100644
Binary files a/jdk-updates-jdk22u-jdk-22+36.tar.gz and b/jdk-updates-jdk22u-jdk-22.0.2+9.tar.gz differ
diff --git a/openjdk-latest.spec b/openjdk-latest.spec
index 748116b2cc1cf1aef75eeba91f125718c46831d1..1fd68bf1310181332aab0ff4b8ebdf834088333e 100644
--- a/openjdk-latest.spec
+++ b/openjdk-latest.spec
@@ -158,7 +158,7 @@
 # Used via new version scheme. JDK 19 was
 # GA'ed in March 2022 => 22.3
 %global vendor_version_string BiSheng
-%global securityver 0
+%global securityver 2
 # buildjdkver is usually same as %%{majorver},
 # but in time of bootstrap of next jdk, it is majorver-1,
 # and this it is better to change it here, on single place
@@ -178,7 +178,7 @@
 %global origin_nice     OpenJDK
 %global top_level_dir_name   %{origin}
 %global minorver        0
-%global buildver        36
+%global buildver        9
 %global rpmrelease      1
 # priority must be 8 digits in total; up to openjdk 1.8, we were using 18..... so when we moved to 11, we had to add another digit
 %if %is_system_jdk
@@ -898,7 +898,7 @@ Name:    java-latest-%{origin}
 Version: %{newjavaver}.%{buildver}
 # This package needs `.rolling` as part of Release so as to not conflict on install with
 # java-X-openjdk. I.e. when latest rolling release is also an LTS release packaged as
-Release: 3
+Release: 0
 
 # java-1.5.0-ibm from jpackage.org set Epoch to 1 for unknown reasons
 # and this change was brought into RHEL-4. java-1.5.0-ibm packages
@@ -1799,6 +1799,9 @@ cjc.mainProgram(arg)
 
 
 %changelog
+* Tue Aug 6 2024 kuenking111 <wangkun49@huawei,com> - 1:22.0.2.9-rolling
+- update to jdk22.0.2+9
+
 * Fri Jul 12 2024 Dingli Zhang <dingli@iscas.ac.cn> - 1:22.0.0.36-3
 - Remove Backport JDK-8316859 for riscv64
 - Fix typo in changelog